[jira] (MRELEASE-653) Filter reactor projects that are concerned by a submodule branch operation

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MRELEASE-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301941#comment-301941 ] 

Robert Scholte commented on MRELEASE-653:
-----------------------------------------

I have my doubts about this patch. This implementation won't work for flat multi-modules projects.
Also, I don't think that nesting the release-plugin (that's what is actually happening here) is a good idea.
IMO you should use the [maven-invoker-plugin|http://maven.apache.org/plugins/maven-invoker-plugin/] to fork a new Maven-call for the branch.
                
> Filter reactor projects that are concerned by a submodule branch operation
> --------------------------------------------------------------------------
>
>                 Key: MRELEASE-653
>                 URL: https://jira.codehaus.org/browse/MRELEASE-653
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: branch
>    Affects Versions: 2.1
>            Reporter: Lucien Weller
>         Attachments: filter-modules.patch
>
>
> We have the requirement to create a separate branch of one submodule when releasing the entire project. We solved this with the follwoing config in pom.xml of concerned submodule:
> {code:xml}
> <profile>
>   <id>branchSubModule</id>
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-release-plugin</artifactId>
>         <inherited>false</inherited>
>         <executions>
>           <execution>
>             <id>explorer-branch</id>
>             <inherited>false</inherited>
>             <phase>package</phase>
>             <goals>
>               <goal>branch</goal>
>             </goals>
>             <configuration>
>               <branchName>re${project.version}-submodule</branchName>
>               <developmentVersion>${project.version}</developmentVersion>
>               <updateBranchVersions>true</updateBranchVersions>
>               <releaseVersion>${project.version}-00-SNAPSHOT</releaseVersion>
>             </configuration>
>           </execution>
>         </executions>
>       </plugin>
>     </plugins>
>   </build>
> </profile>
> {code}
> We launch the release build of parent project with:
> {{mvn release:prepare release:perform -DreleaseProfiles=branchSubModule}}
> Beside issue adressed by MRELEASE-619, we also face the problem that all submodules are affected when our special submodule gets branched.
> We solved this issue by filtering reactor projects with the current working path.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira