[
https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu...
]
Karel Piwko commented on SHRINKRES-214:
---------------------------------------
The issue here is that pom.xml is not an archive, so we just return all dependencies
specified in pom.xml file, that is treating this pom.xml as dependency chain. As there are
no dependencies in jboss-parent, it yields NoResolvedResultException.
I think that we can alter this behavior - if you want to resolve just pom, just want to
resolve metadata only - there is a different feature request to do that.
NoResolvedResultException when trying to resolve a POM
------------------------------------------------------
Key: SHRINKRES-214
URL:
https://issues.jboss.org/browse/SHRINKRES-214
Project: ShrinkWrap Resolvers
Issue Type: Bug
Components: maven
Affects Versions: 2.2.0-beta-1
Reporter: Michael Schnell
Fix For: 2.2.0-cr-1
Trying to resolve a "pom" results in an
org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to resolve
dependencies, none of them were found.
Looking at the local Maven repository, the POM was actually loaded from the remote repo,
but it's not returned:
{code:java}
Maven.resolver().resolve("org.jboss:jboss-parent:pom:12").withoutTransitivity().asSingleFile();
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)