Geoff Howard wrote:
If you havn't read up on the blocks docs on the wiki lately (the last two weeks) you really should. Stefano has put a good series of pages up detailing the plan and the current implementation ideas.
Just a couple of observations -
The usage of /BLOCK-INF may conflict with the Avalon Merlin container /BLOCK-INF which is used to hold avalon block descriptors and related configuration profiles. Usage of "block.xml" also conflict with block.xml used with the Merlin container which is not the same as block.xml used with the Coocon context.
As it seems you've been reading up on those docs can you give your perspective on where our needs differ from what the various Avalon options offer as they exist now and where they seem to be going in the near future?
Geoff
