-
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
[3.8.x][MNG-7400] - Allow more WorkspaceReader's to participate #668
Conversation
ca599fe
to
ccacbd6
Compare
ccacbd6
to
fb0d8b9
Compare
@gnodet thanks for reviewing this, I found a small issue that the ReactorReader was added twice to the list, I fixed this now. |
8f91e6d
to
0dab045
Compare
@gnodet anything left here to do until it could be merged? |
@michael-o is the release manager for 3.8.x branch, so I'll defer to him |
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.
Please synchronize with master.
0dab045
to
f957fa9
Compare
f957fa9
to
5137834
Compare
Merged. |
This is a backport of #667
we at Tycho have a high demand in integrating better with maven to reduce some workarounds that where used in the past to get custom dependency types into the maven dependency model (namely using system scoped absolute paths).
For that reason it would help if it where possible to register additional WorkspaceReader to participate.
I have created a prototype to show/test this new feature.
FYI @mickaelistria @akurtakov
This PR allows maven-extensions to supply
WorkspaceReader
as it is possible withAbstractMavenLifecycleParticipant
currently it is only possible with some workarounds:AbstractMavenLifecycleParticipant
in a maven-core-extensionafterSessionStart
cast theRepositorySystemSession
toDefaultRepositorySystemSession
setWorkspaceReader
and take care not to replace an already exiting oneWith this change it is possible to simply register WorkspaceReader component directly and Maven takes care of all the rest.
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] SUMMARY
, where you replaceMNG-XXX
and
SUMMARY
with the appropriate JIRA issue. Best practice is to use the JIRA issuetitle 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.