January 2013 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-101) Problem to resolving maven dependencies in shrinkres alpha-7 when dependency is defined in the parent project.

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-101?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-101: --------------------------------------- Due to solder-impl having <scope>runtime</scope>, I expect this was fixed via SHRINKRES-103. Please reopen if that's not the case. > Problem to resolving maven dependencies in shrinkres alpha-7 when dependency is defined in the parent project. > -------------------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-101 > URL: https://issues.jboss.org/browse/SHRINKRES-101 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.0.0-alpha-6 > Environment: maven 3.0.4 > Reporter: José Freitas > Assignee: Andrew Rubinger > Labels: maven > > It seems that "Maven.resolver().loadPomFromFile("pom.xml").resolve(...)" is not resolving dependencies from effectivepom, cause it cannot find dependencies defined at the parent. > Please take a look at the gist below to understand the issue better: > https://gist.github.com/4451555 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-103) Maven resolver unable to resolve dependencies with explicit version

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-103?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-103. ----------------------------------- Fix Version/s: 2.0.0-alpha-7 Resolution: Done > 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 > Fix For: 2.0.0-alpha-7 > > > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-103) Maven resolver unable to resolve dependencies with explicit version

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-103?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-103: --------------------------------------- Pushed upstream in https://github.com/shrinkwrap/resolver/commit/7481ccd0dd9d165e74fee50ec7b... Test pushed here: https://github.com/shrinkwrap/resolver/blob/7481ccd0dd9d165e74fee50ec7bdb... > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-103) Maven resolver unable to resolve dependencies with explicit version

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-103?page=com.atlassian.jira.plu... ] Karel Piwko reassigned SHRINKRES-103: ------------------------------------- Assignee: Karel Piwko > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-103) Maven resolver unable to resolve dependencies with explicit version

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-103?page=com.atlassian.jira.plu... ] Karel Piwko moved SHRINKWRAP-438 to SHRINKRES-103: -------------------------------------------------- Project: ShrinkWrap Resolvers (was: ShrinkWrap) Key: SHRINKRES-103 (was: SHRINKWRAP-438) Affects Version/s: 2.0.0-alpha-6 (was: resolver-2.0.0-alpha-1) Component/s: impl-maven (was: ext-resolver) > 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 > > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-102) Maven resolver unable to resolve test-jar dependency

by jay shaughnessy (JIRA)

jay shaughnessy created SHRINKRES-102: ----------------------------------------- Summary: Maven resolver unable to resolve test-jar dependency Key: SHRINKRES-102 URL: https://issues.jboss.org/browse/SHRINKRES-102 Project: ShrinkWrap Resolvers Issue Type: Bug Affects Versions: 2.0.0-alpha-6 Environment: Win7, Maven 3.0.4, Java7 Reporter: jay shaughnessy Assignee: Andrew Rubinger 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>${project.groupId}</groupId> <artifactId>rhq-core-client-api</artifactId> <version>${project.version}</version> <type>test-jar</type> <scope>test</scope> </dependency> ... </dependencies> And the following SW-2 code: MavenResolverSystem resolver = Maven.resolver(); resolver.loadPomFromFile("pom.xml").resolve("org.rhq:rhq-core-client-api:jar:tests:4.6.0-SNAPSHOT).withTransitivity().as(JavaArchive.class) I don't get an exception but the retuened Archive is the production jar: rhq-core-client-api-4.6.0-SNAPSHOT.jar As opposed to the expected test jar: rhq-core-client-api-4.6.0-SNAPSHOT-tests.jar The test jar is generated by us in that module's pom, using the maven-jar plugin with phase=package and goal=test-jar, which I believe is the standard mechanism. And both of the jars are available in my M2 repo in the same place (.m2/repository/org/rhq/rhq-core-client-api/4.6.0-SNAPSHOT). At the moment I have not been able to find a workaround. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-438) Maven resolver unable to resolve dependencies with explicit version

by jay shaughnessy (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-438?page=com.atlassian.jira.pl... ] jay shaughnessy commented on SHRINKWRAP-438: -------------------------------------------- Sorry, perhaps this should have been under the Shrinkwrap Resolvers Project. > Maven resolver unable to resolve dependencies with explicit version > ------------------------------------------------------------------- > > Key: SHRINKWRAP-438 > URL: https://issues.jboss.org/browse/SHRINKWRAP-438 > Project: ShrinkWrap > Issue Type: Bug > Components: ext-resolver > Affects Versions: resolver-2.0.0-alpha-1 > Environment: Win7, Maven 3.0.4, Java7 > Reporter: jay shaughnessy > > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-438) Maven resolver unable to resolve dependencies with explicit version

by jay shaughnessy (JIRA)

jay shaughnessy created SHRINKWRAP-438: ------------------------------------------ Summary: Maven resolver unable to resolve dependencies with explicit version Key: SHRINKWRAP-438 URL: https://issues.jboss.org/browse/SHRINKWRAP-438 Project: ShrinkWrap Issue Type: Bug Components: ext-resolver Affects Versions: resolver-2.0.0-alpha-1 Environment: Win7, Maven 3.0.4, Java7 Reporter: jay shaughnessy 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-243) Dependencies does not find remote repositories set in settings.xml

by jay shaughnessy (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-243?page=com.atlassian.jira.pl... ] jay shaughnessy commented on SHRINKWRAP-243: -------------------------------------------- Karel, I upgraded our version to the Arquillian 1.0.3.Final bom, and the problem did not go away. I thought this pulled in the 2.0.0.alpha-7 version of the resolver but looking more closely at the pom, I don't think it does. I will have to play some dependency games in my pom to use the updated resolver. I'll let you know the result... > Dependencies does not find remote repositories set in settings.xml > ------------------------------------------------------------------ > > Key: SHRINKWRAP-243 > URL: https://issues.jboss.org/browse/SHRINKWRAP-243 > Project: ShrinkWrap > Issue Type: Feature Request > Components: ext-resolver > Reporter: Aslak Knutsen > Assignee: Karel Piwko > Fix For: 1.0.0-alpha-12 > > > Using activeDefault profiles in settings.xml does not seem to be included in the remote repository resolution in Dependencies. > e.g. > .m2/settings.xml > <profiles> > <profile> > <activation> > <activeByDefault>true</activeByDefault> > </activation> > <repositories> > <repository> > <id>jboss-public-repository-group</id> > <name>JBoss Public Repository Group</name> > <url>http://repository.jboss.org/nexus/content/groups/public/</url> > <layout>default</layout> > <releases> > <enabled>true</enabled> > <updatePolicy>never</updatePolicy> > </releases> > <snapshots> > <enabled>true</enabled> > <updatePolicy>never</updatePolicy> > </snapshots> > </repository> > </repositories> > <pluginRepositories> > <pluginRepository> > <id>jboss-public-repository-group</id> > <name>JBoss Public Repository Group</name> > <url>http://repository.jboss.org/nexus/content/groups/public/</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>true</enabled> > </snapshots> > </pluginRepository> > </pluginRepositories> > </profile> > </profiles> -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-433) Race condition deadlock in TarGz Exporter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-433?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on SHRINKWRAP-433: ---------------------------------------------------- Marek Novotny <mnovotny(a)redhat.com> changed the Status of [bug 875031|https://bugzilla.redhat.com/show_bug.cgi?id=875031] from NEW to MODIFIED > Race condition deadlock in TarGz Exporter > ----------------------------------------- > > Key: SHRINKWRAP-433 > URL: https://issues.jboss.org/browse/SHRINKWRAP-433 > Project: ShrinkWrap > Issue Type: Bug > Components: impl-base > Affects Versions: 1.0.1 > Environment: RHEL6 32bit + Oracle JDK 6, Oracle JDK 7, OpenJDK 7 > Windows 2008 32 bit + Oracle JDK 7 > Solaris 10 32 bit + Oracle JDK 6, Oracle JDK 7 > Reporter: Karel Piwko > Assignee: Michal Matloka > Fix For: 1.1.1 > > > There is a deadlock which is triggered on various platforms concerning handling of TarGz archives. Concerned environments are listed in the environment field. > Following error is logged by Jenkins > {code} > 11:48:05 Running org.jboss.shrinkwrap.impl.base.exporter.TarGzExporterTestCase > 16:45:04 Build timed out (after 300 minutes). Marking the build as aborted. > {code} -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues January 2013