[
https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu...
]
Karel Piwko commented on SHRINKRES-140:
---------------------------------------
As for the plugin, I have figure out following:
1/ aether-api/impl/spi is by default not available on plugin classpath
2/ you need to mess with ClassRealm to get access to Aether libraries
3/ however, you get libraries packaged in Maven. In Maven 3.1.0 or 3.1.1, there is
0.9.0.M2, in Resolver we rely on 0.9.0.M4
4/ while when used externally it does not matter, in plugin it does
5/ we rely on aether-connector packages, that were not released for 0.9.0.M2, but there
might be alternatives
6/ Maven 3.2.0 experimental build is still using 0.9.0.M2
So, there are two options:
a/ We can downgrade to 0.9.0.M2.
b/ We can drop plugin goal dependency tree
Seems to me it would be better to use the same deps as available in Maven. Good part is
with changed Maven setup, we would actually verify SHRINKRES-26.
.
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