Pros: remove some duplication of project.xml content across subprojects
Cons: some conent can be inherited, some cannot. solution does not work across all subprojects which may have unique needs.
Theres too much of a release manager level maven customization required to get the packaging right in src and build distributions. Its better to just have each project maintain its project.xml content, then just use basic search and replace strategies to update the contents. I'm using them now and its alot easier than forcing each release manager into a specific deployment strategy.
the current issue with the build tag is a strong example of how extending shoots the projects in the foot. I'm not convinced that the Maven folks have fully worked out the extend mechanism anyways, there are limitations in inhertiance of POM configuration, of properties and of maven.xml goals that just make this inhertance flimsy.
My opinion is that we should keep the customization to a minimum and try to use the Maven defaults wherever possible. This way we can get this over sooner and get back to developing components.
-Mark
David Graham wrote:
Why do you want to duplicate this common info in each project.xml instead of using commons-build/project.xml? Isn't that the purpose of extending the parent file?
David
--- "Mark R. Diggory" <[EMAIL PROTECTED]> wrote:
Yes, the following info has been added to each file (this is just CLI as<url>http://jakarta.apache.org/commons/${pom.artifactId.substring(8)}/</url>
an example):
<pomVersion>3</pomVersion>
<!-- unique project info for each project was retained here -->
<id>commons-cli</id>
<name>CLI</name>
<currentVersion>1.0</currentVersion>
<inceptionYear>2002</inceptionYear>
<shortDescription>Commons CLI</shortDescription>
<description>Commons CLI provides a simple API for working with the command line arguments and options.</description>
<logo>/images/logo.png</logo>
<package>org.apache.commons.${pom.artifactId.substring(8)}</package><siteDirectory>/www/jakarta.apache.org/commons/${pom.artifactId.substring(8)}/</siteDirectory>
<organization>
<name>The Apache Software Foundation</name>
<url>http://jakarta.apache.org</url>
<logo>http://jakarta.apache.org/images/original-jakarta-logo.gif</logo>
</organization>
<licenses> <license> <name>The Apache Software License, Version 2.0</name> <url>/LICENSE.txt</url> <distribution>repo</distribution> </license> </licenses>
<!-- if a project already had a gumpRepository id, it was used over this one -->
<gumpRepositoryId>jakarta</gumpRepositoryId>
<issueTrackingUrl>http://issues.apache.org/bugzilla/</issueTrackingUrl>
<siteAddress>jakarta.apache.org</siteAddress>
<distributionDirectory>/www/jakarta.apache.org/builds/jakarta-commons/${pom.artifactId.substring(8)}/</distributionDirectory>
<connection>scm:cvs:pserver:[EMAIL PROTECTED]:/home/cvspublic:jakarta-commons/${pom.artifactId.substring(8)}</connection>
<repository>
<url>http://cvs.apache.org/viewcvs/jakarta-commons/${pom.artifactId.substring(8)}/</url>
</repository><archive>http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]</archive>
<mailingLists>
<mailingList>
<name>Commons Dev List</name>
<subscribe>[EMAIL PROTECTED]</subscribe>
<unsubscribe>[EMAIL PROTECTED]</unsubscribe>
</mailingList><archive>http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]</archive>
<mailingList>
<name>Commons User List</name>
<subscribe>[EMAIL PROTECTED]</subscribe>
<unsubscribe>[EMAIL PROTECTED]</unsubscribe>
</mailingList> </mailingLists>
David Graham wrote:
Can you be more specific about what changes you're proposing?project.xml
David
--- "Mark R. Diggory" <[EMAIL PROTECTED]> wrote:
This mostly a heads up. I've got a version of each projects
minus the includes and with all the information that was being shared across the commons-build.project.xml. I just want to let everyone know__________________________________
before I commit. Here is a list of projects that will be effected and not effected
All the previous information in each project.xml is intact, I'm only adding info that was previously inherited.
Projects this change will update (these were extending the commons-build/project.xml):
beanutils
betwixt
cli
codec
collections
configuration
daemon
dbcp
dbutils
digester
discovery
el
fileupload
io
jxpath
lang
latka
launcher
logging
math
modeler
net
pool
primitives
validator
Projects this change will not update (these were not extending the commons-build/project.xml):
httpclient
jelly
jexl
I trying to verify that the change will not break builds, but you probibly know your project better than I do. It would be helpful to verify that you can still build properly.
-Mark
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
