[shrinkwrap-issues] [JBoss JIRA] Commented: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.

[Aslak Knutsen (JIRA)]

    [ https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617807#comment-12617807 ] 

Aslak Knutsen commented on SHRINKWRAP-312:
------------------------------------------

> Yes, but I didn't use resolveAs(GenericArchive.class). I used resolveFiles or something similar.

Yea, that shouldn't matter here...

> Now, I did add a direct parent path in the child POM but it didn't help.

direct parent path? you mean:
{code:xml}
<parent>
  ...
  <relativePath>../pom.xml</relativePath>
</parent>
{code}



> ShrinkWrap MavenResolver unable to resolve version from parent POM.
> -------------------------------------------------------------------
>
>                 Key: SHRINKWRAP-312
>                 URL: https://issues.jboss.org/browse/SHRINKWRAP-312
>             Project: ShrinkWrap
>          Issue Type: Bug
>          Components: ext-resolver
>    Affects Versions: 1.0.0-beta-5
>         Environment: Windows 7, Java 6
>            Reporter: Michal Huniewicz
>              Labels: maven-resource-dependency-plugin
>
> All versions of artifacts are stored in the parent POM as Maven properties. There is a dependencyManagement section where they are used.
> When a child project uses Maven dependency resolver to load artifacts, the version cannot be established with MavenDependencyResolver.
> Sample parent POM:
> https://github.com/m1key/audiolicious/blob/master/pom.xml

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira