[ 
https://issues.apache.org/jira/browse/MRESOLVER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521085#comment-16521085
 ] 

Robert Scholte commented on MRESOLVER-17:
-----------------------------------------

Right now maven-artifact-resolver has no dependency on maven(-core), which is 
IMO a very good separation of concern.
What is the issue you're trying to solve with this change?

> Re-parent maven-resolver-provider to maven-resolver (github pull request #3)
> ----------------------------------------------------------------------------
>
>                 Key: MRESOLVER-17
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-17
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: resolver
>            Reporter: Simon Spero
>            Priority: Minor
>              Labels: github-import
>
> [This project doesn't seem to be set up to auto-create issues for pull 
> requests in JIRA]  
> See https://github.com/apache/maven-resolver/pull/3
> History is preserved, hence the seemingly large number of commits. 
> The actual  new commits are at the end, and are changes to the poms, plus a 
> couple of minimal doc comments to avoid checkstyle fail. 
> The changes to the poms mostly involve version bumps to try and get as many   
> plexus versions as possible to line up (provider was failing to find classes.)
> Wagon was bumped to latest release. 
> The version of the maven dependencies is configurable  ; the pull request 
> uses 3.3.9. 
> ---------------------
> PR comment:
> The changes make maven-resolver-provider a sub-project of maven-resolver, 
> instead of the main maven repository.
> These changes allow maven-resolver-provider to be built against maven-3.3.9.
> This might make it easier to create a release version of the entire 
> maven-resolver-suite, with version numbers in the maven-resolver sequence, 
> rather than the maven line.
> Fortunately, the missing OSGI metadata in the jar manifests makes the drop in 
> version numbers less problematic. It would be nice to have these jars be 
> bundles again, since aether is used for provisioning OSGI bundles by 
> containers like Apache Karaf.
> Plexus versions are not quite all lined up, but the provider provides (which 
> is more than it did before the version bumping).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to