VMware offers training and certification to turbo-charge your progress.Learn more
Between Rod's recent blog on the origins of the Interface name, a recent thread querying the renaming of Acegi Security, and a suggestion late last year from my colleague Ben Hale to blog about the origins of the "Acegi" name, I've decided that it's probably time to do so!
First of all, the pronunciation: it's "ah-see-gee". Now that we've got that out of the way, let's go through where it came from:
For those of you who haven't heard of the Spring portfolio, you'll be hearing more about it over the coming months. Spring is really a family of related products with comparable technical and cultural dimensions. Every product in the Spring portfolio shares a consistent quality of architecture, key design patterns, codebase, documentation, test coverage, friendly community, open source licensing, integrated samples, release roadmap and availability of commercial services (such as in-depth training and support) from Interface21.
Renaming Acegi Security to Spring Security reinforces its position in the Spring portfolio and its commitment to the aforementioned principles. Whilst I will continue to lead the project, my association with Interface21 and repositioning of Acegi Security into the Spring portfolio provides access to a broader range of skills and resources from our global team. Furthermore, Acegi Security's roadmap will be aligned with other Interface21-led Spring portfolio products, which benefits the entire Spring community by providing consistent direction.
We also anticipate this repositioning will enhance adoption of Acegi Security. Our customers have told us that their corporate standards teams already approve of Spring Framework, so the repositioning will help developers obtain approval to use its integrated security module. A larger community also delivers more peer-to-peer community support, patches, feature suggestions, bug reports and developers.
These changes will be noticeable with release 1.1.0, which will offer namespace support and require Spring 2. At that point the product will be renamed, and package names will also change. We don't anticipate the package renaming will cause any difficulties, as the move to namespaces also means a move to the new simplified configuration format that so many people have asked for. As such, people would likely be changing their configurations anyway. For those wishing to preserve the old configuration format, simply use find and replace. We won't be changing the acegisecurity-developer mailing list or Subversion repository any time soon.
As you can imagine, these changes are not being taken lightly and have been carefully considered. We believe that it is in the best interests of the overall Spring community that a comprehensive and integrated product portfolio is available, leading to easier adoption, richer integrated samples, quality literature, a stronger community, and availability of professional services. I am pleased that Acegi Security will play its part in the Spring product portfolio, and the enhancements that this repositioning will deliver to everyone concerned.