January 2013 - shrinkwrap-issues - Jboss List Archives

[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 reassigned SHRINKRES-102: ------------------------------------- Assignee: Karel Piwko > 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 > > 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-97) Allow MavenImporter to be configured

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-97?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-97: --------------------------------- Assignee: (was: Andrew Rubinger) > Allow MavenImporter to be configured > ------------------------------------ > > Key: SHRINKRES-97 > URL: https://issues.jboss.org/browse/SHRINKRES-97 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Karel Piwko > > Current SHRINKRES-61 implementation does not allow passing settings.xml. This is an API change and therefore must hit an alpha stream. -- 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-100) Allow Maven resource filtering to be applied for resources imported via MavenImporter

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-100?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-100: ---------------------------------- Assignee: (was: Andrew Rubinger) > Allow Maven resource filtering to be applied for resources imported via MavenImporter > ------------------------------------------------------------------------------------- > > Key: SHRINKRES-100 > URL: https://issues.jboss.org/browse/SHRINKRES-100 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Reporter: Karel Piwko > > When packaging resources to via MavenImporter, any filters defined on the path are ignored. Add support for applying filters. -- 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: ---------------------------------- Assignee: (was: Andrew Rubinger) > 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 > > 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-96) Separate lifecycle for build-resources package

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-96?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-96: --------------------------------- Assignee: (was: Andrew Rubinger) > Separate lifecycle for build-resources package > ---------------------------------------------- > > Key: SHRINKRES-96 > URL: https://issues.jboss.org/browse/SHRINKRES-96 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: build-resources > Affects Versions: 2.0.0-alpha-6 > Reporter: Karel Piwko > > Build resources are mostly static. We should change its release cycle and depend on a non-snapshot version. > That way we will get rid of pom.xml parsing warning in IDE (Eclipse), as plugin execution cannot rely on a project being available from workspace due to security constraints. See JBIDE-13147 for more details on that. -- 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-98) Add support of EAR in MavenImporter

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-98?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-98: --------------------------------- Assignee: (was: Andrew Rubinger) > Add support of EAR in MavenImporter > ----------------------------------- > > Key: SHRINKRES-98 > URL: https://issues.jboss.org/browse/SHRINKRES-98 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Reporter: Karel Piwko > > SHRINKRES-61 implementation does not support EAR archives. A processor able to handle ears must be created. -- 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-99) Add support for applying includes/excludes when defining package resource

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-99?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-99: --------------------------------- Assignee: (was: Andrew Rubinger) > Add support for applying includes/excludes when defining package resource > ------------------------------------------------------------------------- > > Key: SHRINKRES-99 > URL: https://issues.jboss.org/browse/SHRINKRES-99 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Karel Piwko > > SHRINKRES-61 does not honor <includes> and <excludes> from pom.xml file. Therefore, the resulting archive might not 100% match the archive build by Maven. > {code:xml} > <resource> > <includes> > </includes> > <excludes> > </excludes> > </resource> > {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

[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 closed SHRINKRES-101. --------------------------------- Resolution: Duplicate Issue > 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] (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 reassigned SHRINKRES-101: ------------------------------------- Assignee: Karel Piwko (was: Andrew Rubinger) > 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 > > 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-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 updated SHRINKRES-101: ---------------------------------- Fix Version/s: 2.0.0-alpha-7 > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues January 2013