Ah for got about that idea :) For those that are forgetful like me:
http://mail-archives.apache.org/eyebrowse/ReadMsg? [EMAIL PROTECTED]&msgNo=10243
So how about we instead move geronimo/modules/assembly to geronimo/distributions/standard, which will leave then name "assembly" open to the individual configuration modules when we have a tool that can build the configurations one by one.
-dain
-- Dain Sundstrom Chief Architect Gluecode Software 310.536.8355, ext. 26
On Dec 3, 2004, at 10:57 AM, Jeremy Boynes wrote:
This seems similar to the idea of making each configuration a separate artifact.
So rather than one huge assemby module, we would have a separate module (presumably under a different directory than module) for each configuration being generated and then a distribution module that pulls them together into the final package.
-- Jeremy
Dain Sundstrom wrote:Having the assembly as part of the main build is proving to be very troublesome due to the inter-project dependencies. I propose we move geronimo/modules/assembly to geronimo/assembly/standard. This will allow us room to create produce multiple assembled servers from our build.
Unless there is an objection, I'd like to do this this weekend.
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
