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

[Karel Piwko (JIRA)]

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

Karel Piwko commented on SHRINKRES-140:
---------------------------------------

I have asked about versioning because we have a plenty of people that are waiting for Maven 3.1.x support. Yet, we have some plans to add stuff in 2.1.0, such as Gradle importer. I don't want to make Maven 3.1.x support only part of 2.1.0-alpha-2 and force people wait until we release 2.1.0, they won't move from stable to alpha. Maybe we could just make 2.1.0, make 2.1.0-aplha-1 content + Gradle a part of 2.2.0-alpha-1 and directly continue on 2.2.0-alpha-1 development.

BTW, I still haven't fixed the plugin - it's dependency-tree goal. I have no idea what is going weird there, for some reason Maven is not putting some of aether libs on classpath no matter what I do. If we are going to release next minor version, I would be for dropping that functionality ;-)

[~mmatloka] as I fix the plugin, I'll run the sample app ;-).


                
> 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