Merlin is an Avalon sandbox project that includes a set of containment facilities, a container, and a number of container extensions.
http://avalon.apache.org/sandbox/merlin/index.html
The project contains generic containment facilities for meta management, meta data generation, component assembly, deployment, and decommissioning. These facilities provide the infrastructure on which the Merlin container is built. Te container provides support for:
* automated assembly * pluggable deployment strategies * pluggable context management * hierarchical containment * composite components
In addition there are a number of extensions:
* JNDI access, * Servlet support, * Maven plugin extensions
In addition there is support for interactive JNLP based JMX navigation and management in the pipeline along with more comprehensive JNDI support.
Over the last few months the level of interest and activity in Merlin has been growing. In addition I have received several requests for a release of Merlin by people that want to get involved by really need a release before jumping in.
Doing a release has several benefits:
* will facilitate broader feedback from users * will facilitate the expansion of the development community * will enable classic binary downloads for people without CVS access
In earlier emails I have posted details of the technical things I wanted to clean up before a release - all of these items are now complete. As such, Merlin is ready and suitable for handling application style component deployment. When I say "application style" I'm referring to the deployment of components relative to a file system (as distinct from deployment relative to an unpacked war file).
Some of the actions I think should be taken before a release include the following:
1. additional tutorials covering:
- custom contextualization
- dynamic components
2. complete the documentation about the James example
3. add documentation concerning the Merlin/Maven plugin
3. resolve a manifest generation problem that is currently
preventing the proper management of extensions
4. either release Excalibur Extension or include a fork
under the Merlin project
5. make sure everything is in sync with the recent
Excalibur releases
6. tag the CVS
7. vote on a releaseAny volunteers out there willing to help with release preparation - please let me know. Help can be in all sorts of areas - validating documentation, packaging, testing, etc.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
