-
Notifications
You must be signed in to change notification settings - Fork 2.8k
MNG-4463: Version ranges cannot be used for artifacts with 'import' scope #64
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
Conversation
MNG-4463: allow pom import support version range resolution.
MNG-4463: Version ranges cannot be used for artifacts with 'import' scope
|
Please squash your commits into a single commit. |
|
The other commit is on branch, does it matter? |
|
Generally the changes need to be squashed into a single commit and for changes to core you need a corresponding integration test. The integration tests can be found here https://github.com/apache/maven-integration-testing |
|
I'll look into the integration test part. |
|
Since These differences are not described in @jvanzyl Should @phang98 adapt the javadoc or harmonize the behaviour? |
|
@barthel Please squash! |
|
@michael-o Sorry. I'm not the owner of this PR. I only push that change forward. |
|
Hi guys, |
|
No problem, the 3.3.10 release took so much longer than expected so everyone's schedules got thrown off. Either @michael-o or myself will look at it when you're ready. No rush. |
|
@phang98 any news yet on merging this pull request and getting it into the different 3.0.x, 3.1.x, ... maven versions? |
|
Also, is there a corresponding integration test? I will be offline for the most part over the next two weeks. I'm working on a Maven 4.x branch that touches almost everything so I can work on this provided the integration tests pass. By integration test I mean a test project with an integration test that exercises the new proposed behaviour here: https://github.com/apache/maven-integration-testing |
|
I apologize for not fulfill my earlier commitment. :( |
|
No problem, many of us were on holiday and we'll sort it out eventually. |
|
@phang98 any idea when this will get integrated in a maven release? Preferably already in an small 3.0.x maven version as our setup currently requires it. |
|
Thanks for the effort. |
…scope o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
…scope o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
…scope o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
…scope o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
…scope o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
…scope o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
Closes apache#64 without merging. ITs are pending to be committed.
…scope o Extended the 'ModelResolver' interface to support resolving 'Dependency's in addition to 'Parent's. Closes #64 without merging. ITs are pending to be committed.
Closes #64 without merging. ITs are pending to be committed.
Closes #64 without merging. ITs are pending to be committed.
Closes #64 without merging. ITs are pending to be committed.
Closes #64 without merging. ITs are pending to be committed.
Closes #64 without merging. ITs are pending to be committed.
Closes #64 without merging. ITs are pending to be committed.
Closes #64 without merging. ITs are pending to be committed.
|
Resolve #8104 |
MNG-4463: Version ranges cannot be used for artifacts with 'import' scope
This is a quick patch to support version range resolution for artifacts with pom import.