On Wednesday 21 July 2004 12:19, David Leangen wrote: > Would you agree that this is the best approach?
First of all, one should look at your execution environment. You are using embedding, instead of Merlin-standalone, so I assume there must be something in that which is important, and is needed to be identified. Once that is done; Look at what you are trying yo do with Merlin. In effect, there are really two types of 'components', native and aggregated (a.k.a. blocks). It means that every block file that you create can be used as a component in other projects. So, it is important to recognize that the block file is a valuable artifact in its own right. That means, you should probably store native components (and a default block.xml) in a single Jar, and then have 'aggregated' blocks stored in your repository as stand-alone single files, which can be requested independently. They in turn will pick up its composited components from their repo locations. We have not yet devised a system for repository-based block.xmls, and I am not sure whether something formal is required or not, but worthwhile thinking of. YOU should remove your hardcoded block reference "target/deliverables/..." and make it a soft reference, and a way to communicate from the execution environment to your bootstrap code. (In the stand-alone scenario it is a command-line argument). Such reference can either be file or URL relative. Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
