I tried to release a project with 3.0.0-M2 and potentially it is another problem related to
MRELEASE-1038 rfscholte olamy
In our corporate POM we have a pluginManagement entry:
<plugin> <artifactId>maven-release-plugin</artifactId> <version>2.5.3</version> <configuration> <mavenExecutorId>forked-path</mavenExecutorId> <useReleaseProfile>false</useReleaseProfile> <releaseProfiles>cloudbees-internal-release</releaseProfiles> </configuration> </plugin>
My project extends it and has no settings related to the release plugin
In my user settings I have
<activeProfiles> <activeProfile>cloudbees-internal-deploy</activeProfile> <activeProfile>cloudbees-snapshots</activeProfile> <activeProfile>apache-staging</activeProfile> </activeProfiles>
Then I release my project using 3.0.0-M2 with
mvn org.apache.maven.plugins:maven-release-plugin:3.0.0-M2:prepare org.apache.maven.plugins:maven-release-plugin:3.0.0-M2:perform
The perform step is taking my user profiles but not the ones from "releaseProfiles"
[INFO] Executing: /bin/sh -c cd /Users/arnaud/some/path/target/checkout && /Users/arnaud/.asdf/installs/maven/3.6.3/bin/mvn -s /var/folders/bw/j0tmy8p52szfms6c7qb0tx2r0000gn/T/release-settings4094445863857985100.xml -f pom.xml deploy -P cloudbees-internal-deploy,cloudbees-snapshots,apache-staging -f pom.xml
Not sure if it could be because I call the release plugin with the full GAV but it is strange ...
- is related to
MRELEASE-1038 releaseProfiles get overriden by exec.pomFileName
- links to