Re: Suggestions for Starting?

[Stephen McConnell]

J Aaron Farr wrote:

Steve,

Thanks for your advice and prompt reply. I'll further investigate both
Fortress and Merlin, but I think I'll try Merlin since I really would
like to contribute a little to the project and I don't mind keeping up
with the API changes.

Sounds great.

Current Merlin 2.0 version is under the following CVS. I've also included details on how to run the demo to confirm you build is ok:

cvs: jakarta-avalon-excalibur/assembly

$ cd <your-assembly-dir>
$ ant
$ merlin src\etc\kernel.xml

Running the "merlin" command is basically the same as running
the follwowing java command.

java -Djava.ext.dirs=.\extensions -jar .\extensions\merlin-2.0a.jar src\etc\kernel.xml

The current development effort is going into a refactored version of Merlin that seperates out the containerment architecture form the component assembly and deployment architecture. The updated assembly and deployment aspects are available at:

cvs: avalon-sandbox/assembly

$ cd <sandbox-assembly-dir>
$ ant test

The Merlin 2.1 (the uses the seperated assembly content) is incomplete - there is still more work to be done on the container management that is incorporating ideas concerning seperation of the kernel and container defintions, container deployment unit called blocks. That should be complete in a couple of weeks.

cvs: avalon-sandbox/assembly

$ cd <sandbox-merlin-dir>
$ ant test

In which case should I keep an eye on the 'dev'
list as well or should the 'users' least be sufficient?

Most of the feedback from user's experimenting with Merlin is on the user list and most of the information about Merlin updates and direction is posted here. When you get into nitty gritty details of the containment architecture, then this typically pops up on avalon-dev. Based on the Merlin refactoring, this should not have a big impact on Merlin itself, instead - it wil have impact on the assembly API. In general changes on the container APIs will not impoact users unless users are getting into bleeding edge stuff like container specialization and so on. Even then, changes are not too dramatic.

Cheers, Steve.


--

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net




--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>