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:41:00 UTC
[jira] [Updated] (MRELEASE-653) Filter reactor projects that are
concerned by a submodule branch operation
[ https://issues.apache.org/jira/browse/MRELEASE-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold updated MRELEASE-653:
-------------------------------------------
Priority: Minor (was: Major)
> Filter reactor projects that are concerned by a submodule branch operation
> --------------------------------------------------------------------------
>
> Key: MRELEASE-653
> URL: https://issues.apache.org/jira/browse/MRELEASE-653
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.1
> Reporter: Lucien Weller
> Priority: Minor
> 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 was sent by Atlassian Jira
(v8.3.4#803005)