[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-103) Maven resolver unable to resolve dependencies with explicit version
Karel Piwko (JIRA)
jira-events at lists.jboss.org
Sat Jan 12 08:27:21 EST 2013
[ https://issues.jboss.org/browse/SHRINKRES-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745514#comment-12745514 ]
Karel Piwko commented on SHRINKRES-103:
---------------------------------------
Pushed upstream in https://github.com/shrinkwrap/resolver/commit/7481ccd0dd9d165e74fee50ec7bdb4f96fc8cc79
Test pushed here: https://github.com/shrinkwrap/resolver/blob/7481ccd0dd9d165e74fee50ec7bdb4f96fc8cc79/impl-maven/src/test/java/org/jboss/shrinkwrap/resolver/impl/maven/integration/PomDependenciesUnitTestCase.java#L214
> Maven resolver unable to resolve dependencies with explicit version
> -------------------------------------------------------------------
>
> Key: SHRINKRES-103
> URL: https://issues.jboss.org/browse/SHRINKRES-103
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: impl-maven
> Affects Versions: 2.0.0-alpha-6
> Environment: Win7, Maven 3.0.4, Java7
> Reporter: jay shaughnessy
> Assignee: Karel Piwko
>
> Actual version: 2.0.0-alpha-6 (not in the version drop down)
> A possible regression as similar code, using the old API, worked for me with Shrinkwrap-1.
> Example: given the following dependency in the local pom.xml:
> <dependencies>
> ...
> <dependency>
> <groupId>org.powermock</groupId>
> <artifactId>powermock-api-mockito</artifactId>
> <version>${powermock.version}</version>
> <scope>test</scope>
> </dependency>
> ...
> </dependencies>
> And the following SW-2 code:
> MavenResolverSystem resolver = Maven.resolver();
> resolver.loadPomFromFile("pom.xml").resolve("org.powermock:powermock-api-mockito").withTransitivity().as(JavaArchive.class)
> I get the follwoing exception:
> org.jboss.shrinkwrap.resolver.api.ResolutionException: Unable to get version for dependency specified by org.powermock:powermock-api-mockito, it was not provided in <dependencyManagement> section.
> Again, this worked for me in SW-1.
> If I do in fact create a <dependencyManagement> section in the pom, and define the version there, it works as a workaround. But it would seem that an explicit <version> element in the <dependency> should be sufficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the shrinkwrap-issues
mailing list