At 3:47 PM -0500 3/23/04, Ted Husted wrote:
At this point, we're down to whether to organize the subprojects (units of release) into multiple modules or around top-level-directories in a single module.
My only feeling is that should we start inviting some of the popular extensions to join us, the module approach seems like it would scale better.
I don't have a very strong opinion about it. However, from a Maven perspective, if we want to share resources such as a common project.xml, having multiple modules leaves us with no place to put the shared project. I've also had reasonably good results with the maven "multiproject" goal for building a number of related projects, which would also require a shared project.xml
I just to try build Struts with Maven, what am I doing wrong?
[EMAIL PROTECTED] [175] > maven java:compile
__ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT
Attempting to download commons-validator-1.1.2-dev.jar. WARNING: Failed to download commons-validator-1.1.2-dev.jar. The build cannot continue because of the following unsatisfied dependency:
commons-validator-1.1.2-dev.jar (try downloading from http://jakarta.apache.org/commons/validator/)
Total time: 6 seconds Finished at: Tue Mar 23 22:11:19 GMT 2004
-- Peter Pilgrim __ _____ _____ _____ / //__ // ___// ___/ + Serverside Java / /___/ // /__ / /__ + Struts / // ___// ___// ___/ + Expresso Committer __/ // /__ / /__ / /__ + Independent Contractor /___//____//____//____/ + Intrinsic Motivation On Line Resume || \\===> `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
