[
https://issues.jboss.org/browse/AS7-1403?page=com.atlassian.jira.plugin.s...
]
Juergen Zimmermann commented on AS7-1403:
-----------------------------------------
As discussed in
https://issues.jboss.org/browse/SHRINKWRAP-295 there is a problem when
Arquillian tests require artifacts from a maven repo, and these artifacts are lookup up
using the ShrinkWrap class MavenDependencyResolver.
Then you'll get this Maven dependency hierarchy:
* jboss-as-arquillian-container-remote:7.0.0.Final
* jboss-as-arquillian-common:7.0.0.Final
* shrinkwrap-resolver-impl-maven:1.0.0-beta-2 (!)
It took me almost a week to realize that not the current ShrinkWrap version is used, but
an old one. After manually extending my pom.xml with the current artifact
shrinkwrap-resolver-impl-maven:1.0.0-beta-5 the issue was gone.
To find this incompatibility is really frustrating. Is there no chance to provide the
up-to-date version of shrinkwrap-resolver-impl-maven?
Excluded/Banned transitive dependencies for Maven Dependency Resolver
are too strict
------------------------------------------------------------------------------------
Key: AS7-1403
URL:
https://issues.jboss.org/browse/AS7-1403
Project: Application Server 7
Issue Type: Bug
Components: Build System
Affects Versions: 7.0.0.Final
Reporter: Karel Piwko
Assignee: Paul Gier
During 7.0.0.CR1 build, there was a decision to remove transitive dependencies from other
projects and exclude/ban them in jboss-as-parent.
This decision has effectively crippled usage of Maven Dependency Resolver, which
wasn't used in CR1-date based testsuite, so the change passed silently.
If user wants to use the ShrinkWrap Dependency Resolver in the AS7 testsuite, he
won't get the required transitive dependencies, such as wagon or aether, so the
resolver is unusable.
According to disscussion with Vladimir, it would help "to flatten" dependency
tree for ShrinkWrap dependency Resolver, however, that's only the part of the
solution, the restrictions posed in AS7 parent must be relaxed afterwards.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira