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 Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-101?page=com.atlassian.jira.plu... ] Michal Matloka commented on SHRINKRES-101: ------------------------------------------ "Problem to resolving maven dependencies in shrinkres alpha-7" in alpha-7 or in alpha-6? According to description affected alpha-6. > 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: Karel Piwko > Labels: maven > Fix For: 2.0.0-alpha-7 > > > 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] (SHRINKDESC-142) Support Java EE 5 Web Descriptor

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-142?page=com.atlassian.jira.pl... ] Andrew Rubinger resolved SHRINKDESC-142. ---------------------------------------- Assignee: Ralf Battenfeld Fix Version/s: 2.0.0-alpha-5 Resolution: Done Upstream: https://github.com/shrinkwrap/descriptors/commit/97e245f97a1411dcee803c4e... > Support Java EE 5 Web Descriptor > -------------------------------- > > Key: SHRINKDESC-142 > URL: https://issues.jboss.org/browse/SHRINKDESC-142 > Project: ShrinkWrap Descriptors > Issue Type: Feature Request > Reporter: Ralf Battenfeld > Assignee: Ralf Battenfeld > Fix For: 2.0.0-alpha-5 > > -- 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: ---------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Thomas SEGISMONT (was: Karel Piwko) Fix Version/s: 2.0.0-alpha-8 Resolution: Done Pushed upstream. > 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: Thomas SEGISMONT > Labels: maven, resolver > Fix For: 2.0.0-alpha-8 > > > 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 commented on SHRINKRES-105: --------------------------------------- Pushed upstream in https://github.com/shrinkwrap/resolver/commit/9b12af8823baba8480b10de40ab... > 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 commented on SHRINKRES-105: --------------------------------------- Thanks Thomas! I'll merge your commit to make it a part of next release in few next days. With 2.0.0-alpha-7, the best workaround is then to specify a path to default settings.xml via API: {code} Maven.configureResolver().fromFile("~/.m2/settings.xml") {code} You should be able use this until next version is out. > 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 Thomas SEGISMONT (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Thomas SEGISMONT edited comment on SHRINKRES-105 at 1/21/13 5:03 AM: --------------------------------------------------------------------- In SHRINKRES-42, the fix makes possible to resolve variables if the user specifies a particular settings file. But for default settings XML file, the Maven {code:java}SettingsBuildingRequest{code} is built in {code:java}org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder{code} not in {code:java}org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl{code} was (Author: tsegismont): In SHRINKRES-42, the fix makes possible to resolve variables if the user specifies a particular settings file. But for default settings XML file, the Maven {code:java}SettingsBuildingRequest{code} is built in {code:java}org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder{code} not {code:java}org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl{code} > 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 Thomas SEGISMONT (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Thomas SEGISMONT commented on SHRINKRES-105: -------------------------------------------- In SHRINKRES-42, the fix makes possible to resolve variables if the user specifies a particular settings file. But for default settings XML file, the Maven {code:java}SettingsBuildingRequest{code} is built in {code:java}org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder{code} not {code:java}org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl{code} > 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 Thomas SEGISMONT (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Thomas SEGISMONT updated SHRINKRES-105: --------------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/shrinkwrap/resolver/pull/34 > 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 Thomas SEGISMONT (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Thomas SEGISMONT reopened SHRINKRES-105: ---------------------------------------- Not fixed by 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: 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-103) Maven resolver unable to resolve dependencies with explicit version

by jay shaughnessy (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-103?page=com.atlassian.jira.plu... ] jay shaughnessy commented on SHRINKRES-103: ------------------------------------------- Karel, confirming that this is fixed in alpha-7, thanks! > 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 > Priority: Critical > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues January 2013