[JBoss JIRA] (SHRINKRES-210) Dependency management with scopes are not resolved correctly
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-210?page=com.atlassian.jira.plu... ]
Matous Jobanek updated SHRINKRES-210:
-------------------------------------
Fix Version/s: (was: 3.0.0)
> Dependency management with scopes are not resolved correctly
> ------------------------------------------------------------
>
> Key: SHRINKRES-210
> URL: https://issues.jboss.org/browse/SHRINKRES-210
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven
> Affects Versions: 2.2.0-beta-1
> Reporter: Emond Papegaaij
>
> If the scope of an indirect dependency is changed in the dependencyManagement of your pom, this scope is not correctly taken into account when resolving compileAndRuntimeDependencies. I've created a very minimal testcase to demonstrate this problem:
> https://github.com/papegaaij/resolve-dep
> This testcase resolves the dependencies using:
> {code}
> File[] jars = Maven.configureResolver().workOffline()
> .loadPomFromFile("pom.xml")
> .importCompileAndRuntimeDependencies().resolve()
> .withTransitivity().as(File.class);
> {code}
> The pom only defines 1 compile dependency (shrinkwrap-impl-base), which depends on 2 others (shrinkwrap-api and shrinkwrap-spi). shrinkwrap-api has a dependencyManagement with scope provided, so I expect this resolution to yield 2 files (base and spi), but it yields all 3.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (SHRINKRES-214) NoResolvedResultException when trying to resolve a POM
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu... ]
Matous Jobanek updated SHRINKRES-214:
-------------------------------------
Fix Version/s: (was: 3.0.0)
> NoResolvedResultException when trying to resolve a POM
> ------------------------------------------------------
>
> Key: SHRINKRES-214
> URL: https://issues.jboss.org/browse/SHRINKRES-214
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven
> Affects Versions: 2.2.0-beta-1
> Reporter: Michael Schnell
>
> Trying to resolve a "pom" results in an org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to resolve dependencies, none of them were found.
> Looking at the local Maven repository, the POM was actually loaded from the remote repo, but it's not returned:
> {code:java}
> Maven.resolver().resolve("org.jboss:jboss-parent:pom:12").withoutTransitivity().asSingleFile();
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (SHRINKRES-282) Resolve just a pom.xml
by Paolo Antinori (JIRA)
Paolo Antinori created SHRINKRES-282:
----------------------------------------
Summary: Resolve just a pom.xml
Key: SHRINKRES-282
URL: https://issues.jboss.org/browse/SHRINKRES-282
Project: ShrinkWrap Resolvers
Issue Type: Bug
Affects Versions: 2.2.6
Reporter: Paolo Antinori
What's the correct way to resolve a pom.xml ? My use case is to obtain a BOM.
{code}
Maven.resolver().resolve("org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:pom:3.0.0-beta-2").withoutTransitivity().asFile();
{code}
{code}
MavenResolvedArtifact artifact = Maven.resolver().resolve("org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:pom:3.0.0-beta-2").withoutTransitivity()
.asSingle(MavenResolvedArtifact.class);
{code}
they both fail? Am I doing something wrong or is this behavior broken for pom files?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months