You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jesse Foster <je...@verizonbusiness.com> on 2009/11/11 04:37:45 UTC

Multi-Module Project and Release Plugin

I'm trying to branch our code from trunk using the Maven Release Plugin . 
When I try to do a dry run with the release plugin it complains about
missing scm information when all parent poms have scm sections.  I'm
guessing the plugin is expecting a scm section in the root pom.xml, but I
didn't put one there as the pom just aggregates the whole project together. 
Is there a way around this or am I forced to run the release plugin for each
module independently?

Thanks,
Jesse


Project layout:

pom.xml (Aggregate parent)
Common-libraries
- pom.xml (Aggregate and Inheritance Parent)
- multiple modules building libraries for use across applications
Common-components
- pom.xml (Aggregate and Inheritance Parent)
- multiple modules building jar and wars containing api's and common web
apps( provisioning, etc. )
Application-A
- pom.xml (Aggregate and Inheritance Parent)
- api-jar
- webapp
- ear
Application-B
- pom.xml (Aggregate and Inheritance Parent)
- api-jar
- webapp
- ear
Application-C
- pom.xml (Aggregate and Inheritance Parent)
- api-jar
- webapp
- ear
Packaging Pom
- pom.xml (Aggregate and Inheritance Parent)
- Big Ear (Pulls all jars and wars together for one unified ear ready for
deployment)
- assembly (Zips together a jboss distribution, our jboss config files, and
ear for final package)

Applications A-C use jars and wars from common-libraries and
common-components.  These applications must run within our environment and a
standalone environment, thus they build their own ears.  All of the
applications are isolated from one another as well; you can check out
Application-C and compile it by itself without needing code from the common
projects(the jars get pushed to our internal maven repository).  This also
means the Applications have their own trunk, tags, and branches so they can
be developed separately from the main codeline.

As mentioned above the root pom.xml is just an aggregate parent so it
literally just has modules listed in it.
-- 
View this message in context: http://old.nabble.com/Multi-Module-Project-and-Release-Plugin-tp26295544p26295544.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Multi-Module Project and Release Plugin

Posted by EJ Ciramella <ec...@upromise.com>.
I personally never use the release plugin (another case of the "maven way" not fitting with "our way"), but I wonder, if you ran "mvn site", wouldn't each step along the way not only generate site output, but also have links to the scm details for that particular tier?  If that's the case, why not have scm details at each level?

I guess I'm half asking half curious to see other replies...



-----Original Message-----
From: Jesse Foster [mailto:jesse.foster@verizonbusiness.com] 
Sent: Tuesday, November 10, 2009 10:38 PM
To: users@maven.apache.org
Subject: Multi-Module Project and Release Plugin


I'm trying to branch our code from trunk using the Maven Release Plugin . 
When I try to do a dry run with the release plugin it complains about
missing scm information when all parent poms have scm sections.  I'm
guessing the plugin is expecting a scm section in the root pom.xml, but I
didn't put one there as the pom just aggregates the whole project together. 
Is there a way around this or am I forced to run the release plugin for each
module independently?

Thanks,
Jesse


Project layout:

pom.xml (Aggregate parent)
Common-libraries
- pom.xml (Aggregate and Inheritance Parent)
- multiple modules building libraries for use across applications
Common-components
- pom.xml (Aggregate and Inheritance Parent)
- multiple modules building jar and wars containing api's and common web
apps( provisioning, etc. )
Application-A
- pom.xml (Aggregate and Inheritance Parent)
- api-jar
- webapp
- ear
Application-B
- pom.xml (Aggregate and Inheritance Parent)
- api-jar
- webapp
- ear
Application-C
- pom.xml (Aggregate and Inheritance Parent)
- api-jar
- webapp
- ear
Packaging Pom
- pom.xml (Aggregate and Inheritance Parent)
- Big Ear (Pulls all jars and wars together for one unified ear ready for
deployment)
- assembly (Zips together a jboss distribution, our jboss config files, and
ear for final package)

Applications A-C use jars and wars from common-libraries and
common-components.  These applications must run within our environment and a
standalone environment, thus they build their own ears.  All of the
applications are isolated from one another as well; you can check out
Application-C and compile it by itself without needing code from the common
projects(the jars get pushed to our internal maven repository).  This also
means the Applications have their own trunk, tags, and branches so they can
be developed separately from the main codeline.

As mentioned above the root pom.xml is just an aggregate parent so it
literally just has modules listed in it.
-- 
View this message in context: http://old.nabble.com/Multi-Module-Project-and-Release-Plugin-tp26295544p26295544.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


______________________________________________________________________
This e-mail has been scanned by Verizon Managed Email Content Service, using Skeptic? technology powered by MessageLabs. For more information on Verizon Managed Email Content Service, visit http://www.verizonbusiness.com.
______________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org