1.) The issue of common dependencies could be resolved by parameterizing things like the location that dependency jars are downloaded to so that all scripts use the same location.
2.) I'm not impressed that anyone would ever want to download the entire commons as a src zip and compile it. Its modularity, and its separate release cycles for each module really make such an effort have no value (IMHO). When I need a commons module, I go and get just that module, thats the whole power of having everything separate. Why would/should I compile that digester when all I wanted was lang? I say keep things well separated, otherwise the user will suffer.
-Mark
Stephen Colebourne wrote:
Our maven scripts now depend on commons-build, however this is of course not included in the release zips. This is a problem and means that maven cannot be used in releases.
Anyone got any ideas on how to solve this? I don't like the idea of hacking project xml for each release.
Stephen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
