[
https://issues.jboss.org/browse/SHRINKRES-241?page=com.atlassian.jira.plu...
]
Toby Crawley commented on SHRINKRES-241:
----------------------------------------
This is happening in WildFly Swarm. I did some digging and it looks
like the 3.2.1 version comes from
{{org.wildfly:wildfly-parent:10.0.0.Final}}, transitively, and we are
importing that pom in {{<dependencyManagement>}}. We're forcing 3.2.5
with an explicit dependency as you suggested.
The parent pom that imports {{wildfly-parent}} and
{{shrinkwrap-resolver-impl-maven}} (via an import of
{{arquillian-bom}}) is
https://github.com/wildfly-swarm/wildfly-swarm-core/blob/master/pom.xml.
Now that we have at least a partial understanding of where 3.2.1 is
coming from, I don't really consider this a SHRINKRES issue.
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)