]
Karel Piwko edited comment on SHRINKRES-182 at 5/28/14 4:40 AM:
----------------------------------------------------------------
Fix pushed upstream in
ShrinkWrap Resolver sometimes can't resolve a dependency with EJB
packaging
---------------------------------------------------------------------------
Key: SHRINKRES-182
URL:
https://issues.jboss.org/browse/SHRINKRES-182
Project: ShrinkWrap Resolvers
Issue Type: Bug
Components: impl-maven
Affects Versions: 2.1.0
Reporter: Ron Šmeral
Assignee: Karel Piwko
Fix For: 2.1.1, 2.2.0-alpha-3
Several Seam example integration tests fail when creating the deployment for testing, due
to an exception in resoution of the {{org.jboss.seam:jboss-seam}} artifact, which is an
artifact with EJB packaging.
{noformat}
java.lang.RuntimeException: Could not invoke deployment method: public static
org.jboss.shrinkwrap.api.Archive
org.jboss.seam.example.booking.test.BookingTest.createDeployment()
...
Caused by: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to
collect/resolve dependency tree for a resolution due to: Could not find artifact
org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository
...
Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find
artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository
...
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find
artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository
...
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact
org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository
{noformat}
It is quite suspicious, that SWR tries to download a file with an {{ejb}} extension,
which would be obviously wrong:
{noformat}
WARNING: Failed downloading
org/jboss/seam/jboss-seam/2.3.4.Final-redhat-1/jboss-seam-2.3.4.Final-redhat-1.ejb from
file:///qa/hudson_workspace/workspace/wfk-2.x-seam-2.3-eap6-itest/dc63a4c9/wfk-qa/build/configuration/../../../jboss-wfk-2.6.0-maven-repository/.
{noformat}
This behaviour is seemingly not consistent, but is deterministic - it happens only in
some projects, but in those, it happens every time.