-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[MNG-6261] - using java File api to compare #192
Conversation
maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelBuilder.java
Outdated
Show resolved
Hide resolved
maven-model-builder/src/test/java/org/apache/maven/model/building/FileModelSourceTest.java
Show resolved
Hide resolved
Looks also good according to https://builds.apache.org/job/maven-box/job/maven/job/MNG-6261/ |
c6816c4
to
e50878f
Compare
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.
Nice work.
I left some minor comment
maven-model-builder/src/test/java/org/apache/maven/model/building/FileModelSourceTest.java
Outdated
Show resolved
Hide resolved
maven-model-builder/src/test/java/org/apache/maven/model/building/FileModelSourceTest.java
Outdated
Show resolved
Hide resolved
maven-model-builder/src/main/java/org/apache/maven/model/building/FileModelSource.java
Outdated
Show resolved
Hide resolved
ca5d156
to
9f07b03
Compare
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.
+1 (non binding)
+1 And one more small testcase - should pass before/after patch
|
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.
LGTM
fix: Add lifecycle mapping metadata for M2E (Eclipse)
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MNG-XXX] - Fixes bug in ApproximateQuantiles
,where you replace
MNG-XXX
with the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verify
to make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.