Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.1
-
Fix Version/s: None
-
Component/s: branch
-
Labels:None
-
Patch Submitted:Yes
-
Number of attachments :
Description
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:
<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>
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.
Issue Links
- depends upon
-
MRELEASE-619
release:branch doesn't work as expected with multi-module projects
-
