[
https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu...
]
Michal Matloka edited comment on SHRINKRES-140 at 6/25/13 5:06 PM:
-------------------------------------------------------------------
Last eclipse aether version was released in february. I have tried then to perform
migration
https://github.com/mmatloka/resolver/tree/ECLIPSE_AETHER_NOT_WORKING . However
as far as I remember the problem was in maven-aether-provider which still uses the
sonatype aether. It seems that maven-aether-provider 3.1.0-alpha-1 was relead on
01-Jun-2013 and uses already the eclipse one. Migration concerns import changes, but also
they have performed some minor api refactors.
was (Author: mmatloka):
Last eclipse aether version was released in february. I have tried then to perform
migration
https://github.com/mmatloka/resolver/tree/ECLIPSE_AETHER_NOT_WORKING . However
as far as I remember the problem was in maven-aether-provider. It seems that
maven-aether-provider 3.1.0-alpha-1 was relead on 01-Jun-2013 and uses already the eclipse
one aether.
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: Andrew Rubinger
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