[ 
https://jira.codehaus.org/browse/MRELEASE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lucien Weller updated MRELEASE-672:
-----------------------------------

    Attachment: MRELEASE-672.patch

Patch coresponding to changes made in git
                
> branching a sub module during a build
> -------------------------------------
>
>                 Key: MRELEASE-672
>                 URL: https://jira.codehaus.org/browse/MRELEASE-672
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: branch
>    Affects Versions: 2.1
>         Environment: maven-release-plugin 2.1 with SVN
>            Reporter: Lucien Weller
>         Attachments: MRELEASE-672.patch
>
>
> We have to requirement to create a reparate branch of a part of your source 
> tree (concretely a sub module) somtime when building the entire tree. We 
> automated this with a profile in pom.xml of that sub-module where we 
> configured branch goal as part of packag phase with something like this:
> {code:xml}
> <profile>
>       <id>makeBranch</id>
>       <build>
>               <plugins>
>                       <plugin>
>                               <groupId>org.apache.maven.plugins</groupId>
>                               <artifactId>maven-release-plugin</artifactId>
>                               <executions>
>                                       <execution>
>                                               <id>make-branch</id>
>                                               <phase>package</phase>
>                                               <goals>
>                                                       <goal>branch</goal>
>                                               </goals>
>                                               <configuration>
>                                                       
> <branchName>re${project.version}-branch</branchName>
>                                                       
> <developmentVersion>${project.version}</developmentVersion>
>                                                       
> <updateBranchVersions>true</updateBranchVersions>
>                                                       
> <releaseVersion>${project.version}-00-SNAPSHOT</releaseVersion>
>                                               </configuration>
>                                       </execution>
>                               </executions>
>                       </plugin>
>               </plugins>
>       </build>
> </profile>
> {code}
> Unfortunately we faced two problems:
> * Scm URL was not correctly handled for sub-module, acording path of module. 
> This issue was already solved for Tagging in release preparation (see 
> MRELEASE-261). We ported the fix for branching.
> * With actual implementation all projects of a reactor build are considered 
> by branch goal. We solved this issue by filtering projects according their 
> relative 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

        

Reply via email to