January 2015 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-214) NoResolvedResultException when trying to resolve a POM

by Michael Schnell (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu... ] Michael Schnell commented on SHRINKRES-214: ------------------------------------------- Sounds good to me. > 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 > Fix For: 2.2.0-cr-1 > > > 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 (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-215) Bug in implementation of Packaging.of("type")

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-215: ------------------------------------- Summary: Bug in implementation of Packaging.of("type") Key: SHRINKRES-215 URL: https://issues.jboss.org/browse/SHRINKRES-215 Project: ShrinkWrap Resolvers Issue Type: Bug Components: maven Affects Versions: 2.2.0-beta-1 Reporter: Karel Piwko Fix For: 2.2.0-cr-1 There is a wrong usage of putIfAbsent() in Packaging.of(), see https://github.com/shrinkwrap/resolver/commit/ee71e55cee525c6985c973542df... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-214) NoResolvedResultException when trying to resolve a POM

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-214: --------------------------------------- Something like: {code} Maven.configureResolver().resolveOnlyMetadata().resolve("org.jboss:jboss-parent:pom:12").withoutTransitivity().asSingleFile() {code} Would that work? > 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 > Fix For: 2.2.0-cr-1 > > > 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 (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-214) NoResolvedResultException when trying to resolve a POM

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-214: --------------------------------------- The issue here is that pom.xml is not an archive, so we just return all dependencies specified in pom.xml file, that is treating this pom.xml as dependency chain. As there are no dependencies in jboss-parent, it yields NoResolvedResultException. I think that we can alter this behavior - if you want to resolve just pom, just want to resolve metadata only - there is a different feature request to do that. > 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 > Fix For: 2.2.0-cr-1 > > > 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 (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-214) NoResolvedResultException when trying to resolve a POM

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-214: ---------------------------------- Fix Version/s: 2.2.0-cr-1 > 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 > Fix For: 2.2.0-cr-1 > > > 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 (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues January 2015