[JBoss JIRA] Created: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
10:37 a.m.
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
Affects Versions: 1.0.0-beta-5
Environment: Windows 7, Java 6
Reporter: Michal Huniewicz
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
10:57 a.m.
New subject: [JBoss JIRA] Commented: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Aslak Knutsen commented on SHRINKWRAP-312:
------------------------------------------
Are you using loadMetadataFromPom() ?
{code}
DependencyResolvers.use(MavenDependencyResolver.class)
.loadMetadataFromPom("pom.xml")
.artifact("org.jboss.weld.servlet:weld-servlet")
.resolveAs(GenericArchive.class))
{code}
{code}
/**
* Loads remote repositories for a POM file. If repositories are defined in
* the parent of the POM file and there are accessible via local file
* system, they are set as well.
*
* These remote repositories are used to resolve the artifacts during
* dependency resolution.
*
* Additionally, it loads dependencies defined in the POM file model in an
* internal cache, which can be later used to resolve an artifact without
* explicitly specifying its version.
*
* @param pathx
* A path to the POM file, must not be {@code null} or empty
* @return A dependency builder with remote repositories set according to
* the content of POM file.
* @throws Exception
*/
MavenDependencyResolver loadMetadataFromPom(String path) throws ResolutionException;
{code}
If you are, then it might be that you need a direct dependency on the artifact in the pom
for it to be resolved.
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
10:57 a.m.
New subject: [JBoss JIRA] Updated: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Aslak Knutsen updated SHRINKWRAP-312:
-------------------------------------
Component/s: ext-resolver
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
11:04 a.m.
New subject: [JBoss JIRA] Commented: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Michal Huniewicz commented on SHRINKWRAP-312:
---------------------------------------------
Hi Aslak,
Yes, but I didn't use resolveAs(GenericArchive.class). I used resolveFiles or
something similar.
Now, I did add a direct parent path in the child POM but it didn't help.
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
12:09 p.m.
New subject: [JBoss JIRA] Commented: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
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
12:24 p.m.
New subject: [JBoss JIRA] Commented: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Michal Huniewicz commented on SHRINKWRAP-312:
---------------------------------------------
Yes, that's what I put there. Didn't help.
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
4:16 p.m.
New subject: [JBoss JIRA] Commented: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Aslak Knutsen commented on SHRINKWRAP-312:
------------------------------------------
Have you tried adding a dependency on the artifact in parent (not just via
dependencyManagement) ?
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
4:18 p.m.
New subject: [JBoss JIRA] Assigned: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Karel Piwko reassigned SHRINKWRAP-312:
--------------------------------------
Assignee: Karel Piwko
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
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
4:20 p.m.
New subject: [JBoss JIRA] Commented: (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Aslak Knutsen commented on SHRINKWRAP-312:
------------------------------------------
Never mind.. just learned you had spoken to kpiwko about this.. I won't dig around for
more info.. :)
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
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
10:46 a.m.
New subject: [JBoss JIRA] (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Karel Piwko updated SHRINKWRAP-312:
-----------------------------------
Fix Version/s: resolver-2.0.0-alpha-1
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
3:54 p.m.
New subject: [JBoss JIRA] (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
Sanne Grinovero commented on SHRINKWRAP-312:
--------------------------------------------
Hello, we're having a failing testcase in Hibernate Search; I *think* it's because
of this issue, and as workaround we explicitly define the same version again in all
modules.
Interesting to note: we can't reproduce it on OSX, it fails on Linux. Also this
affects us only for the log4j test dependency, somehow it's not affecting other
dependencies.
Related to: https://hibernate.onjira.com/browse/HSEARCH-970
(To reproduce: remove the log4j versions from all poms, keeping it defined only in the
parent pom's dependencyManagment - there is only one Arquillian test in the suite, it
fails consistently on my machine; the logs mention the dependency version of log4j not
being defined, and then the deployment doesn't contain all the needed dependencies)
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
5:50 p.m.
New subject: [JBoss JIRA] (SHRINKWRAP-312) ShrinkWrap MavenResolver unable to resolve version from parent POM.
[
https://issues.jboss.org/browse/SHRINKWRAP-312?page=com.atlassian.jira.pl...
]
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
4609
days inactive
4709
days old
shrinkwrap-issues@lists.jboss.org
11 comments
6 participants
participants (6)
-
Aslak Knutsen (JIRA) -
Karel Piwko (Commented) (JIRA)
-
Karel Piwko (JIRA)
-
Karel Piwko (Updated) (JIRA)
-
Michal Huniewicz (JIRA)
-
Sanne Grinovero (Commented) (JIRA)