Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[MRELEASE-1109] Snapshot detection and support for versions like
${revision}${sha1}${changelist}
#202base: master
Are you sure you want to change the base?
[MRELEASE-1109] Snapshot detection and support for versions like
${revision}${sha1}${changelist}
#202Changes from 11 commits
21df8de
ab5c8d5
466383d
0ad7bb6
ef93eec
27791ef
66f51ce
dbcbb08
4032941
6b4fc81
e3682ab
fbc3ac2
0be8e5a
56fe3ed
28ebea0
fe02232
491ee0d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was
System.getProperty()
used before? We tend not to rely on system properties, but only on Maven properties.@cstamas @slawekjaranowski
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
sha1
property for CI is usually passed from a command-line. This class is an extract of everything related to CI Friendly. See, the usage of this method, it's used inJDomModel
which does not have Maven project reference.The goal of
CiFriendlyVersion
is a small clean up without a big refactoring.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a contradiction to https://github.com/apache/maven/blob/5e977034565ffc50c6b073f21fab50fae71705dd/maven-api-impl/src/main/java/org/apache/maven/internal/impl/model/DefaultModelVersionProcessor.java#L51-L62 because they can only come from model or Maven user properties...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll revert it back to
System
those properties do not exist inMavenProject
because the current maven version for this plugin defined as<mavenVersion>3.2.5</mavenVersion>
but you've put a link to the changes made 2 months ago.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is not correct. The class has been modified long time ago by me. Check its history. I can find the JIRA, if you want. The release of Maven Release will upgrade to 3.6.3 anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is the change: https://issues.apache.org/jira/browse/MNG-7658. Model properties do get overwritten with the user properties. It is expected to work properly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But it does not with the current dependencies defined in this project :) Just run the integration test and you will see it
maven-release-plugin/src/it/projects/prepare/ci-friendly-multi-module
Then the huge problem is the current dependencies defined in the pom.xml. It's just dependency hell that does not work if everything is set up as it's defined.
First of all,
mavenVersion=3.2.5
, the project even does not compile withmaven-3.2.5
binary, it is immediately failed bymaven-enforce-plugin
and requires3.6.3
version.Then if you try to bump
mavenVersion
to 3.6.3 and the binary to the same version, it fails again.Taking all this dependency incompatibility issues, please do not refer to the recent changes, they just don't work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's pause this until Maven Release is updated to 3.6.3. I will work in this soon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I will update the PR later, it will be nice if you notice me in this thread as soon as you finish maven version upgrade.