[
https://issues.jboss.org/browse/SHRINKRES-241?page=com.atlassian.jira.plu...
]
Toby Crawley commented on SHRINKRES-241:
----------------------------------------
Yes, we're seeing exactly SHRINKRES-238.
Thanks for the BOM suggestion. Unfortunately, WildFly Swarm can't use the BOM, since
we need dependencies provided by {{wildfly-parent}} that aren't available in the
BOMs.
We'll stick with a direct dependency on {{maven-aether-provider}} for now.
Wrong maven-aether-provider dependency for some reason
------------------------------------------------------
Key: SHRINKRES-241
URL:
https://issues.jboss.org/browse/SHRINKRES-241
Project: ShrinkWrap Resolvers
Issue Type: Bug
Affects Versions: 2.2.2
Reporter: Bob McWhirter
I can't explain it, because your POM looks good, but if I rely on SW-Resolvers 2.2.2,
which should be using maven-aether-provider 3.2.5, from a maven v3.2.5, I still get
maven-aether-provider 3.2.1.
Can you think of some way to force maven-aether-provider to 3.2.5?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)