[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
Karel Piwko (Commented) (JIRA)
jira-events at lists.jboss.org
Wed Nov 9 11:50:45 EST 2011
[ https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641472#comment-12641472 ]
Karel Piwko commented on SHRINKWRAP-312:
----------------------------------------
Hi Sanne,
this can you try with 2.0.0-alpha-1-SNAPSHOT? I have a working test based on the hibernate-search-archetype and it is working for me.
> 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
> Assignee: Karel Piwko
> Labels: maven-resource-dependency-plugin
> Fix For: resolver-2.0.0-alpha-1
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the shrinkwrap-issues
mailing list