When I run mvn clean, and look at the reactor order, it lists the build order 
for the modules in that particular project. That list does not include other 
projects for which the target project is dependent upon.

For example:

Project A
---> module A
---> module B
---> module C

Project B
---> module A
---> module B


Module A of project A has a dependency on module B of Project B. When I ran mvn 
clean at the top level or project A, it lists the build order (e.g. module B, 
C, A of project A), but there is no mention of module B in Project B. Also, 
module B of project B may have a dependency on module A of a different (project 
C). The goal is to have an ordered list of the projects to be released. In this 
example Project C, then Project B, and then Project A. The reactor does not 
seem to provide that functionality. Maybe I am missing something.

Thanks,
Rob

-----Original Message-----
From: Thiessen, Todd (Todd) [mailto:[email protected]] 
Sent: Friday, May 25, 2012 3:51 PM
To: Maven Users List
Subject: RE: Plugin to determine release order for multiple projects

Can't you just look at the reactor order?  That will tell you which projects 
you would have to release first.

> -----Original Message-----
> From: Pimentel, Robert [mailto:[email protected]]
> Sent: Friday, May 25, 2012 4:47 PM
> To: '[email protected]'
> Subject: Plugin to determine release order for multiple projects
> 
> Hello,
> 
> We currently have about 40 different multi-module projects. To date, 
> we have determined an appropriate release order for the projects by 
> manually parsing the POM files and making note of the dependencies. We 
> keep our list in a spreadsheet, and it is re-evaluated with every 
> release because (a) new projects are added (b) the list of projects 
> being released changes from one release to the next (c) the project 
> interdependencies change. As you can imagine this is both tedious and 
> time-consuming. Do you know of a plugin, or any (preferably free) 
> third-party tools that can parse a collection of project POMs and 
> produce an appropriate release order? Additionally, it would be great 
> if the product could check for circular dependencies. I am at the 
> point where I am going to create something myself, but would prefer 
> not to if something like this already exists.
> Windows Server 2003 SP2
> Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 
> 1.6.0_24
> 
> Thanks,
> Rob

---------------------------------------------------------------------
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]

Reply via email to