In a multi-module Maven project, what could make the parent project not to be a part of the reactor?

2014-08-07 Thread Behrang Saeedzadeh
I was just reading the source code for the [Versions Maven Plugin]( http://mojo.codehaus.org/versions-maven-plugin/), and noticed this snippet of code: if ( reactorProjects.contains( getProject().getParent() ) ) { getLog().info( Project's parent is part of the reactor );

Re: In a multi-module Maven project, what could make the parent project not to be a part of the reactor?

2014-08-07 Thread Stephen Connolly
* When you use -pl to restrict the reactor, * when you use -f to build a specific pom * When the parent is not at the specified relativePath * etc Many reasons On 7 August 2014 12:29, Behrang Saeedzadeh behran...@gmail.com wrote: I was just reading the source code for the [Versions Maven

Re: In a multi-module Maven project, what could make the parent project not to be a part of the reactor?

2014-08-07 Thread Behrang Saeedzadeh
I see. Thanks. Best regards, Behrang http://www.behrang.org On Thu, Aug 7, 2014 at 9:35 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: * When you use -pl to restrict the reactor, * when you use -f to build a specific pom * When the parent is not at the specified relativePath