upgrade maven-release-plugin to 3.0.0-M6 #281
Conversation
olamy
commented
Jul 18, 2022
- Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
- Ensure that the pull request title represents the desired changelog entry
- Please describe what you did
- Link to relevant issues in GitHub or Jira
- Link to relevant pull requests, esp. upstream and downstream changes
- Ensure you have provided tests - that demonstrates feature works or fixes the issue
|
Causes JENKINS-69198. |
|
⇒ #296 |
|
Caused (or contributed to) jenkins-infra/helpdesk#3143. "M" is milestone, right? Why are we using prerelease versions of dependencies? |
|
jenkinsci/plugin-pom#558 did not contain a description of the change, let alone its motivation or the reasoning behind it. |
motivation was this issue https://issues.apache.org/jira/browse/MRELEASE-1025 (some contributors had this issue). Is there any issue logged in https://issues.apache.org/jira/projects/MRELEASE? |
Unclear to me, but both https://maven.apache.org/surefire/maven-surefire-plugin/ and https://maven.apache.org/maven-release/maven-release-plugin/ show "M" versions, and the last releases without an M were released in 2019 and 2015 respectively. Dependabot did not offer them specifically because they have an M and are considered prerelease, but if the Maven project considered them prereleases and was recommending a non-prerelease version for general usage, why would the web pages show the prerelease version, and why would the general usage version be so many years old? Does not make sense to me. |
Contributors on Windows? They could switch to JEP-229 and never need to run MRP locally again, saving the lives of multiple kittens. |
