I'm playing around with the automatic generation of gump files and I'm dealing with the question "how to handle the artifact group". My initial thinking is to generate a gump module per group and to populate the module with all project definitions that are (a) members the group AND (b) under the same source repository.
There is one possible issue I see concerning gump association of a repository (cvs/svn) url to a module. In the usage I envisage, I would be generating something like 15-20 modules to cover the avalon suite. Each module would reference the same svn address. Is that an issue?
Secondly, is it ok to have module names that contain the "/" character (e.g. "avalon/composition")?
Alternatively, what is the feasibility of extending module to support something like:
<module>
<group name="avalon">
<group name="composition">
<project name="avalon-composition-api"/>
<project name="avalon-composition-spi"/>
<project name="avalon-composition-impl"/>
....
</group>
<group/>
...
</module>Cheers, Steve.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
