> From: Paul Hammant [mailto:[EMAIL PROTECTED]] > > Berin, > > >>I do not feel like adding merlin-specific meta descriptors (which is > >>what .xprofile & friends are atm) to a package and then > releasing that > >>package. Reason 1: merlin is alpha. Reason 2: the descriptors are > >>merlin-specific. > >> > >> > > > >I agree. > > > [...] > > How about we package two* jars for cornerstone. One that > includes only > phoenix descriptors and one that containers xml for Merlin. Jars are > named as such. > > The benefit is that people understand that Merlin and Phoenix are > different containers and that for their (say > private/commercial) comps > they only have themselves to make one style of XML config. > > * well given api separation from impl, it will be more than two.
That's fine. Keep in mind that the assembling of the descriptors in Phoenix is a build time phenomenon, while in Merlin it is a development time phenomenon. Let's keep the Merlin descriptors out of the source base, and put it in a build/merlin-compat directory. That way we have two jars: cornerstone-phoenix-VERSION.jar cornerstone-merlin-VERSION.jar I still want to see something where the meta info is embedded in the class itself, but that isn't for Avalon 4. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
