-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
Project has the following config for the maven-release-plugin:
<plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <version>2.5.2</version> <executions> <execution> <id>default</id> <goals> <goal>perform</goal> </goals> <configuration> <pomFileName>${}/pom.xml</pomFileName> </configuration> </execution> </executions> <configuration> <projectVersionPolicyId>OddEvenVersionPolicy</projectVersionPolicyId> </configuration> <dependencies> <dependency> <groupId>org.apache.maven.release</groupId> <artifactId>maven-release-oddeven-policy</artifactId> <version>2.5.2</version> </dependency> </dependencies> </plugin> </plugins>
Current version of the project is 0.0.15-SNAPSHOT
When i do
mvn release:prepare
on the commandline, it correctly suggests 0.0.16 for the release and 0.0.17-SNAPSHOT for the next development version.
When i want to do the release via Jenkins (with Default Versioning Mode set to "None", because every time i try to select one of the other two options, upon save it goes back to "None"), then Jenkins incorrectly suggests 0.0.15 for the release and 0.0.16-SNAPSHOT for the next development version.
[JENKINS-28581] support Maven version policies
Mike Pfaff
created issue -
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
| Summary | Original: m2release plugin doesn't support Maven version policies | New: support Maven version policies |
| Workflow | Original: JNJira [ 163427 ] | New: JNJira + In-Review [ 181235 ] |
| Assignee | Original: James Nord [ teilo ] |