You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/22 12:37:00 UTC
[jira] [Closed] (MRELEASE-672) branching a sub module during a
build
[ https://issues.apache.org/jira/browse/MRELEASE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold closed MRELEASE-672.
------------------------------------------
might be fixed, no one responding; reopen if needed
> branching a sub module during a build
> -------------------------------------
>
> Key: MRELEASE-672
> URL: https://issues.apache.org/jira/browse/MRELEASE-672
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.1
> Environment: maven-release-plugin 2.1 with SVN
> Reporter: Lucien Weller
> Priority: Major
> Labels: github-pullrequest
> 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 was sent by Atlassian Jira
(v8.3.4#803005)