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
[MENFORCER-304] - Improve dependency resolving in multiple modules project #35
Conversation
Ping @olamy |
Seems @olamy is busy. @khmarbaise Would you please take a look at this PR? |
The first thing which I would suggest is to squash your commits into a single commit...makes it easier... |
2bca3b6
to
c17de12
Compare
@khmarbaise Rebased to latest master and squashed commits. :) |
Hi @khmarbaise Any progress yet? |
Hi @khmarbaise Will you include this pull request into the next release? We have been using the maven enforcer with this fix for almost 6 month (custom build) but it would be better if the new official release has the fix. |
@khmarbaise I would also like this feature. Any chance of it getting done? |
Hi @khmarbaise, could you please review and decide? Best |
@elharo , could you please have a look into this PR? |
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.
Looks OK to me. @khmarbaise do you have any concerns?
*/ | ||
public void setReactorProjects( List<MavenProject> reactorProjects ) | ||
{ | ||
this.reactorProjects = reactorProjects; |
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.
make a copy to avoid exposing mutable internal state.
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.reactorProjects = reactorProjects; | |
this.reactorProjects = java.util.Collections.unmodifiableList( reactorProjects ); |
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.
Rebased the PR on latest master, and applied changes as @svenlange suggested :)
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.
@svenlange - but this will only be unmodifiable if referenced via this.reactorProjects
. External code can still alter original reactorProjects
that was sent to setReactorProjects
method...
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.
As it's long time ago when I filed this PR, I can not recall why the getter and setter of reactorProjects
is required. Local build looks OK without the getter and setter . :(
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.
@elharo @svenlange @pzygielo
I've tested and confirmed that the getter and setter of reactorProjects
are redundant. They are removed in latest commit.
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.
Great thanks!
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 this PR is still stuck cause @khmarbaise is not responding. Can anyone else review and decide, @elharo ?
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.
@elharo Friendly ping :)
8f6767a
to
b7162b1
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.
Running CI build now
And? :-) |
@elharo It's weird the master branch build fails. See https://builds.apache.org/blue/organizations/jenkins/maven-box%2Fmaven-enforcer/detail/master/135/pipeline/42/ :( |
Local build with Oracle JDK 1.7.0_79 and maven 3.5.4 is OK.
|
The build is blue now :) https://builds.apache.org/job/maven-box/job/maven-enforcer/job/master/138/ |
I would love to see this improvement released. Are there any plans yet for releasing 3.0.0-M4 of maven-enforcer-plugin? |
Is it possible to trigger a release? @elharo @khmarbaise |
see https://issues.apache.org/jira/browse/MENFORCER-304