So far, here's what works: (this should work right now, unless I've forgotten to commit something)
$ cd path/to/your/local/struts/current/core $ maven dist $ cd ../taglib $ maven dist $ cd ../apps $ maven dist $ cd ../tiles $ maven dist $ cd ../el $ maven dist $ cd ../bsf $ maven dist
Doing this yields several things: - newly built jars in your ${user.home}/.maven/repository/struts/jars struts-1.3.0-dev.jar struts-mailreader-dao-1.3.0-dev.jar struts-taglib-1.3.0-dev.jar struts-tiles-1.3.0-dev.jar
- a full maven distribution in each subproject's target (or m-target) directories
My biggest complaint right now is with the way we are doing things and how much duplication we now have (and will have in the future) wrt maven and ant configuration. Each subproject has it's own copy of project.properties, maven.xml, and 90% of each project.xml is repeated. I've already wasted several hours trying to get these all in sync. I am -1 for keeping each separate for the sake of seperation.
I prefer that we setup our maven project files to extend a single top project.xml under current/site/ (future), like it is done now in commons. This includes the CheckStyle config and license as well as other shared resources.
-- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
