[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

[Andrew Rubinger (JIRA)]

    [ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790559#comment-12790559 ] 

Andrew Rubinger commented on SHRINKRES-140:
-------------------------------------------

What is the motivating force here?  Are there specific updates we need to pull in?  Keep in mind that the implementation we have is working and tested under the hood, and upgrades for upgrades sake can lead to incompatible runtime changes across point releases.  We aim to be as stable as possible at this point, so what is the virtue of swapping the underlying implementation at this time and introducing risk?
                
> Update Aether implementation to org.eclipse.aether one
> ------------------------------------------------------
>
>                 Key: SHRINKRES-140
>                 URL: https://issues.jboss.org/browse/SHRINKRES-140
>             Project: ShrinkWrap Resolvers
>          Issue Type: Component  Upgrade
>          Components: impl-maven
>    Affects Versions: 2.0.0-beta-5
>            Reporter: Karel Piwko
>            Assignee: Michal Matloka
>
> Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version.
> Update should not affect user at all, it should comprise of replacing imports with new ones.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira