-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in 2.14.2: version not updated #888
Comments
Please providee the pom which you're acting upon. And please use the -X option of maven and attach the output. The only change regarding |
here is a minimal pom:
|
Can't reproduce with maven 3.8.6:
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.somewhere.di</groupId>
<artifactId>di-business-model</artifactId>
<version>2.0.6-UpdateVersionsPlugin-SNAPSHOT</version>
<name>di-business-model</name>
<description>Business Model Objects for DI</description>
<properties>
<revision>2.0.6</revision>
<!-- the CI system uses the sha1 property for the branch name - unused
in local builds -->
<sha1></sha1>
<changelist>-SNAPSHOT</changelist>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.source>11</maven.compiler.source>
<maven.compiler.target>11</maven.compiler.target>
</properties>
<build>
<plugins>
<plugin>
<!-- https://mvnrepository.com/artifact/org.codehaus.mojo/versions-maven-plugin -->
<groupId>org.codehaus.mojo</groupId>
<artifactId>versions-maven-plugin</artifactId>
<version>2.14.2</version>
</plugin>
</plugins>
</build>
</project> Once again, please attach debug logs. |
Your project uses CI friendly versions, and properties get resolved in 2.14.2. That's the main difference against 2.14.1. There will be no substitution if the resolved value happens to be the same as the original value. Since this only happens on the CI/CD env, I guess it might have to do with it. Your pom.xml says that the sha1 will assume the value of the branch name; if that happens to be UpdateVersionsPlugin, then the file is not going to be changed. |
your analysis seems correct - 2.14.2 no longer updates the version if you set it to the value that it currently resolves to. Unfortunately we specifically need to set the resolved version, since some tools later in the pipeline cant handle variables in the version :-/ |
Gotcha. I recommend fixing the plugin version until we patch this or there's a workaround. |
…Properties - allows to disable property interpolation, so that it's possible to match against raw property values as well as replace properties with interpolated values if the value is the same as the property value
Hi, I just replaced apache-maven-3.8.6 with apache-maven-3.8.7. I got a fresh repository. I am using org.apache.maven.shared.invoker.DefaultInvoker to run maven programmatically for some years now with no problems. I post my goals using org.apache.maven.shared.invoker.DefaultInvocationRequest. When using "versions:use-next-releases" the invoker fail. I am including the log: please help... Happy new year |
Please create a new issue. |
Ok. |
- allows to disable property interpolation, so that it's possible to match against raw property values as well as replace properties with interpolated values if the value is the same as the property value
Thank you everybody - much appreciated! |
I am currently investigating what i believe to be a regression in versions-maven-plugin 2.14.2.
Basically versions:set no longer seems to work as designed:
the version is unaffected after this
This works in 2.14.1:
Unfortunately this only fails when run in our Jenkins.
I am still investigating this. Any suggestions appreciated.
The text was updated successfully, but these errors were encountered: