[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-243) org.jboss.shrinkwrap.resolver.api.ResolutionException: Unable to get version for dependency specified by ..., it was not provided in neither <dependencyManagement> nor <dependencies> sections.

Matous Jobanek (JIRA) issues at jboss.org
Thu May 12 05:23:00 EDT 2016


     [ https://issues.jboss.org/browse/SHRINKRES-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed SHRINKRES-243.
------------------------------------
      Assignee: Matous Jobanek
    Resolution: Won't Fix


> org.jboss.shrinkwrap.resolver.api.ResolutionException: Unable to get version for dependency specified by ..., it was not provided in neither <dependencyManagement> nor <dependencies> sections.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SHRINKRES-243
>                 URL: https://issues.jboss.org/browse/SHRINKRES-243
>             Project: ShrinkWrap Resolvers
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 2.1.0, 2.2.1, 2.2.2
>         Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
> Java version: 1.8.0_45, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_45\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
>            Reporter: Gunther v. Wolffersdorff
>            Assignee: Matous Jobanek
>         Attachments: sample.zip
>
>
> shrinkwrap-resolver-impl-maven : Unable to get version for dependency specified by ..., it was not provided in neither <dependencyManagement> nor <dependencies> sections.
> In Java EE Project based upon arche type wildfly-javaee7-webapp-ear-archetype we have the following pom-situation:
> - parent-project
>    - ejb-project
>    - web-project ( depends on ejb-project)
> - parent-project defines versions of subprojects by dependency management
> In web-project, if we want to resolve the ejb-project by:
> {{resolver.resolve("de.alvara.ticket:sample-ejb").withoutTransitivity().asSingleFile();}}
> we get: 
> org.jboss.shrinkwrap.resolver.api.ResolutionException: Unable to get version for dependency specified by de.alvara.ticket:sample-ejb:compile, it was not provided in neither <dependencyManagement> nor <dependencies> sections.
> 	at org.jboss.shrinkwrap.resolver.impl.maven.task.ResolveVersionFromMetadataTask.execute(ResolveVersionFromMetadataTask.java:122)
> 	at org.jboss.shrinkwrap.resolver.impl.maven.PomEquippedResolveStageBaseImpl.resolveVersion(PomEquippedResolveStageBaseImpl.java:85)
> 	at org.jboss.shrinkwrap.resolver.impl.maven.ResolveStageBaseImpl.resolveDependency(ResolveStageBaseImpl.java:190)
> 	at org.jboss.shrinkwrap.resolver.impl.maven.ResolveStageBaseImpl.resolveDependency(ResolveStageBaseImpl.java:185)
> 	at org.jboss.shrinkwrap.resolver.impl.maven.ResolveStageBaseImpl.resolve(ResolveStageBaseImpl.java:79)
> 	at org.jboss.shrinkwrap.resolver.impl.maven.ResolveStageBaseImpl.resolve(ResolveStageBaseImpl.java:44)
> 	at ShrinkwrapResolverTest.test(ShrinkwrapResolverTest.java:15)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:497)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the shrinkwrap-issues mailing list