January 2013 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-106) Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional"

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-106?page=com.atlassian.jira.plu... ] Ales Justin commented on SHRINKRES-106: --------------------------------------- Is there a test/example on how to use/setup this? > Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional" > -------------------------------------------------------------------------------------- > > Key: SHRINKRES-106 > URL: https://issues.jboss.org/browse/SHRINKRES-106 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Andrew Rubinger > Assignee: Andrew Rubinger > Fix For: 2.0.0-alpha-7 > > > We currently support only the default Maven behavior with respect to the resolution of transitive dependencies as documented by: > http://maven.apache.org/guides/introduction/introduction-to-dependency-me... > In particular, it's currently impossible to resolve "provided" and "test" scope transitives, as well as those marked "optional". Ales has provided a use case which shall act as the basis for this feature request. -- 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-106) Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional"

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-106?page=com.atlassian.jira.plu... ] Andrew Rubinger updated SHRINKRES-106: -------------------------------------- Git Pull Request: https://github.com/shrinkwrap/resolver/pull/33 > Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional" > -------------------------------------------------------------------------------------- > > Key: SHRINKRES-106 > URL: https://issues.jboss.org/browse/SHRINKRES-106 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Andrew Rubinger > Assignee: Andrew Rubinger > Fix For: 2.0.0-alpha-7 > > > We currently support only the default Maven behavior with respect to the resolution of transitive dependencies as documented by: > http://maven.apache.org/guides/introduction/introduction-to-dependency-me... > In particular, it's currently impossible to resolve "provided" and "test" scope transitives, as well as those marked "optional". Ales has provided a use case which shall act as the basis for this feature request. -- 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-106) Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional"

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-106?page=com.atlassian.jira.plu... ] Andrew Rubinger resolved SHRINKRES-106. --------------------------------------- Resolution: Done Found the magic sauce in Aether, and added some API love to give us hooks. Upstream: https://github.com/ALRubinger/resolver/commit/af3a87e2b48023e23bd77433567... and https://github.com/ALRubinger/resolver/commit/6e125ced05aa93aff55dc03d353.... > Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional" > -------------------------------------------------------------------------------------- > > Key: SHRINKRES-106 > URL: https://issues.jboss.org/browse/SHRINKRES-106 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Andrew Rubinger > Assignee: Andrew Rubinger > Fix For: 2.0.0-alpha-7 > > > We currently support only the default Maven behavior with respect to the resolution of transitive dependencies as documented by: > http://maven.apache.org/guides/introduction/introduction-to-dependency-me... > In particular, it's currently impossible to resolve "provided" and "test" scope transitives, as well as those marked "optional". Ales has provided a use case which shall act as the basis for this feature request. -- 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-106) Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional"

by Andrew Rubinger (JIRA)

Andrew Rubinger created SHRINKRES-106: ----------------------------------------- Summary: Provide Mechanism to Resolve "provided"- and "test"-scoped transitives, and "optional" Key: SHRINKRES-106 URL: https://issues.jboss.org/browse/SHRINKRES-106 Project: ShrinkWrap Resolvers Issue Type: Feature Request Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: 2.0.0-alpha-7 We currently support only the default Maven behavior with respect to the resolution of transitive dependencies as documented by: http://maven.apache.org/guides/introduction/introduction-to-dependency-me... In particular, it's currently impossible to resolve "provided" and "test" scope transitives, as well as those marked "optional". Ales has provided a use case which shall act as the basis for this feature request. -- 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 Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-102?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-102: ---------------------------------- Fix Version/s: 2.0.0-alpha-7 > 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: Karel Piwko > Fix For: 2.0.0-alpha-7 > > > 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] (SHRINKRES-105) Support resolution of variables in Maven settings file

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-105. --------------------------------- Assignee: Karel Piwko Resolution: Duplicate Issue Reopened to change affected version. > Support resolution of variables in Maven settings file > ------------------------------------------------------ > > Key: SHRINKRES-105 > URL: https://issues.jboss.org/browse/SHRINKRES-105 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 1.0.0-beta-7 > Reporter: Thomas SEGISMONT > Assignee: Karel Piwko > Labels: maven, resolver > > Variables in Maven settings file are not resolved. > For instance if you have this node in your settings : > {code:xml} > <localRepository>${user.home}/.m2/repository</localRepository> > {code} > then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- 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-105) Support resolution of variables in Maven settings file

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-105. --------------------------------- Resolution: Duplicate Issue Closing as duplicate of SHRINKRES-42 > Support resolution of variables in Maven settings file > ------------------------------------------------------ > > Key: SHRINKRES-105 > URL: https://issues.jboss.org/browse/SHRINKRES-105 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 2.0.0-alpha-6 > Reporter: Thomas SEGISMONT > Labels: maven, resolver > > Variables in Maven settings file are not resolved. > For instance if you have this node in your settings : > {code:xml} > <localRepository>${user.home}/.m2/repository</localRepository> > {code} > then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- 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-105) Support resolution of variables in Maven settings file

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Karel Piwko reopened SHRINKRES-105: ----------------------------------- > Support resolution of variables in Maven settings file > ------------------------------------------------------ > > Key: SHRINKRES-105 > URL: https://issues.jboss.org/browse/SHRINKRES-105 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 2.0.0-alpha-6 > Reporter: Thomas SEGISMONT > Labels: maven, resolver > > Variables in Maven settings file are not resolved. > For instance if you have this node in your settings : > {code:xml} > <localRepository>${user.home}/.m2/repository</localRepository> > {code} > then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- 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-105) Support resolution of variables in Maven settings file

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-105: ---------------------------------- Affects Version/s: 1.0.0-beta-7 (was: 2.0.0-alpha-6) > Support resolution of variables in Maven settings file > ------------------------------------------------------ > > Key: SHRINKRES-105 > URL: https://issues.jboss.org/browse/SHRINKRES-105 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 1.0.0-beta-7 > Reporter: Thomas SEGISMONT > Labels: maven, resolver > > Variables in Maven settings file are not resolved. > For instance if you have this node in your settings : > {code:xml} > <localRepository>${user.home}/.m2/repository</localRepository> > {code} > then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- 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-105) Support resolution of variables in Maven settings file

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Karel Piwko moved SHRINKWRAP-439 to SHRINKRES-105: -------------------------------------------------- Project: ShrinkWrap Resolvers (was: ShrinkWrap) Key: SHRINKRES-105 (was: SHRINKWRAP-439) > Support resolution of variables in Maven settings file > ------------------------------------------------------ > > Key: SHRINKRES-105 > URL: https://issues.jboss.org/browse/SHRINKRES-105 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Reporter: Thomas SEGISMONT > Labels: maven, resolver > > Variables in Maven settings file are not resolved. > For instance if you have this node in your settings : > {code:xml} > <localRepository>${user.home}/.m2/repository</localRepository> > {code} > then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- 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