February 2013 - shrinkwrap-issues

[JBoss JIRA] (SHRINKRES-62) MavenImporter should support shrinkwrap filtering

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-62?page=com.atlassian.jira.plug... ] Bernard Labno commented on SHRINKRES-62: ---------------------------------------- Required due to SHRINKWRAP-326 > MavenImporter should support shrinkwrap filtering > ------------------------------------------------- > > Key: SHRINKRES-62 > URL: https://issues.jboss.org/browse/SHRINKRES-62 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Karel Piwko > Assignee: Bernard Labno > Priority: Minor > Fix For: 2.0.0-beta-3 > > > Discussed with kpiwko while designing the api for SHRINKWRAP-325. > Should be able to include/exclude any main/test class/resource/webapp-resource. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-62) MavenImporter should support shrinkwrap filtering

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-62?page=com.atlassian.jira.plug... ] Karel Piwko commented on SHRINKRES-62: -------------------------------------- Seems very nice! I have a question, was the update to ShrinkWrap 1.1.1 required, voluntary or unintentional? > MavenImporter should support shrinkwrap filtering > ------------------------------------------------- > > Key: SHRINKRES-62 > URL: https://issues.jboss.org/browse/SHRINKRES-62 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Karel Piwko > Assignee: Bernard Labno > Priority: Minor > Fix For: 2.0.0-beta-3 > > > Discussed with kpiwko while designing the api for SHRINKWRAP-325. > Should be able to include/exclude any main/test class/resource/webapp-resource. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-113) resolving of maven artifacts with classifier failed

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-113?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-113: --------------------------------------- The pattern "groupId:artifactId:jar:classifier" will always hit classifier as a version. If you need to specify classifier and let it resolve the version from pom, do the following: {code} resolve("groupId:artifactId:jar:classifier:?") {code} > resolving of maven artifacts with classifier failed > --------------------------------------------------- > > Key: SHRINKRES-113 > URL: https://issues.jboss.org/browse/SHRINKRES-113 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Juergen Biersack > Assignee: Michal Matloka > > The following code is not working: > {code:title=ArquillianTest.java|borderStyle=solid} > @Deployment > public static EnterpriseArchive createDeployment() { > ... > JavaArchive[] ejbModule = mavenResolver > .resolve("groupId:artifactId:jar:classifier") > .withoutTransitivity() > .as(JavaArchive.class); > ... > } > {code} > The class org.jboss.shrinkwrap.resolver.api.maven.coordinate.MavenCoordinates should be able to interprete the coordinate above with the documented pattern: > *<groupId>:<artifactId>[:<packagingType>[:<classifier>]][:<version>]* > It seems, that the classifier is interpreted as version. > The following workaround is running well: > {code:title=ArquillianTest.java|borderStyle=solid} > @Deployment > public static EnterpriseArchive createDeployment() { > ... > JavaArchive[] warDependenciesClientViews = mavenResolver > .addDependency( > MavenDependencies.createDependency( > MavenCoordinates.createCoordinate( > "groupId", > "artifactId", > null, > PackagingType.JAR, > "classifier"), > null, > false)) > .resolve() > .withoutTransitivity() > .as(JavaArchive.class); > ... > } > {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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-113) resolving of maven artifacts with classifier failed

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-113?page=com.atlassian.jira.plu... ] Michal Matloka reassigned SHRINKRES-113: ---------------------------------------- Assignee: Michal Matloka (was: Andrew Rubinger) > resolving of maven artifacts with classifier failed > --------------------------------------------------- > > Key: SHRINKRES-113 > URL: https://issues.jboss.org/browse/SHRINKRES-113 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Juergen Biersack > Assignee: Michal Matloka > > The following code is not working: > {code:title=ArquillianTest.java|borderStyle=solid} > @Deployment > public static EnterpriseArchive createDeployment() { > ... > JavaArchive[] ejbModule = mavenResolver > .resolve("groupId:artifactId:jar:classifier") > .withoutTransitivity() > .as(JavaArchive.class); > ... > } > {code} > The class org.jboss.shrinkwrap.resolver.api.maven.coordinate.MavenCoordinates should be able to interprete the coordinate above with the documented pattern: > *<groupId>:<artifactId>[:<packagingType>[:<classifier>]][:<version>]* > It seems, that the classifier is interpreted as version. > The following workaround is running well: > {code:title=ArquillianTest.java|borderStyle=solid} > @Deployment > public static EnterpriseArchive createDeployment() { > ... > JavaArchive[] warDependenciesClientViews = mavenResolver > .addDependency( > MavenDependencies.createDependency( > MavenCoordinates.createCoordinate( > "groupId", > "artifactId", > null, > PackagingType.JAR, > "classifier"), > null, > false)) > .resolve() > .withoutTransitivity() > .as(JavaArchive.class); > ... > } > {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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-113) resolving of maven artifacts with classifier failed

by Juergen Biersack (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-113?page=com.atlassian.jira.plu... ] Juergen Biersack updated SHRINKRES-113: --------------------------------------- Description: The following code is not working: {code:title=ArquillianTest.java|borderStyle=solid} @Deployment public static EnterpriseArchive createDeployment() { ... JavaArchive[] ejbModule = mavenResolver .resolve("groupId:artifactId:jar:classifier") .withoutTransitivity() .as(JavaArchive.class); ... } {code} The class org.jboss.shrinkwrap.resolver.api.maven.coordinate.MavenCoordinates should be able to interprete the coordinate above with the documented pattern: *<groupId>:<artifactId>[:<packagingType>[:<classifier>]][:<version>]* It seems, that the classifier is interpreted as version. The following workaround is running well: {code:title=ArquillianTest.java|borderStyle=solid} @Deployment public static EnterpriseArchive createDeployment() { ... JavaArchive[] warDependenciesClientViews = mavenResolver .addDependency( MavenDependencies.createDependency( MavenCoordinates.createCoordinate( "groupId", "artifactId", null, PackagingType.JAR, "classifier"), null, false)) .resolve() .withoutTransitivity() .as(JavaArchive.class); ... } {code} > resolving of maven artifacts with classifier failed > --------------------------------------------------- > > Key: SHRINKRES-113 > URL: https://issues.jboss.org/browse/SHRINKRES-113 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Juergen Biersack > Assignee: Andrew Rubinger > > The following code is not working: > {code:title=ArquillianTest.java|borderStyle=solid} > @Deployment > public static EnterpriseArchive createDeployment() { > ... > JavaArchive[] ejbModule = mavenResolver > .resolve("groupId:artifactId:jar:classifier") > .withoutTransitivity() > .as(JavaArchive.class); > ... > } > {code} > The class org.jboss.shrinkwrap.resolver.api.maven.coordinate.MavenCoordinates should be able to interprete the coordinate above with the documented pattern: > *<groupId>:<artifactId>[:<packagingType>[:<classifier>]][:<version>]* > It seems, that the classifier is interpreted as version. > The following workaround is running well: > {code:title=ArquillianTest.java|borderStyle=solid} > @Deployment > public static EnterpriseArchive createDeployment() { > ... > JavaArchive[] warDependenciesClientViews = mavenResolver > .addDependency( > MavenDependencies.createDependency( > MavenCoordinates.createCoordinate( > "groupId", > "artifactId", > null, > PackagingType.JAR, > "classifier"), > null, > false)) > .resolve() > .withoutTransitivity() > .as(JavaArchive.class); > ... > } > {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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-100) Allow Maven resource filtering to be applied for resources imported via MavenImporter

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-100?page=com.atlassian.jira.plu... ] Bernard Labno commented on SHRINKRES-100: ----------------------------------------- This is heavy stuff. There is many ways user may provide variable values (filter files, project defined properties, system properties). The variables may have different forms: @value@ ${var3} ${project.version} > 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 > Labels: api-change > > 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-113) resolving of maven artifacts with classifier failed

by Juergen Biersack (JIRA)

Juergen Biersack created SHRINKRES-113: ------------------------------------------ Summary: resolving of maven artifacts with classifier failed Key: SHRINKRES-113 URL: https://issues.jboss.org/browse/SHRINKRES-113 Project: ShrinkWrap Resolvers Issue Type: Feature Request Components: api-maven Affects Versions: 2.0.0-beta-2 Reporter: Juergen Biersack Assignee: Andrew Rubinger -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-62) MavenImporter should support shrinkwrap filtering

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-62?page=com.atlassian.jira.plug... ] Andrew Rubinger updated SHRINKRES-62: ------------------------------------- Component/s: (was: api-maven) Note: No API Changes were made as part of resolution of this issue. > MavenImporter should support shrinkwrap filtering > ------------------------------------------------- > > Key: SHRINKRES-62 > URL: https://issues.jboss.org/browse/SHRINKRES-62 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Karel Piwko > Assignee: Bernard Labno > Priority: Minor > Fix For: 2.0.0-beta-3 > > > Discussed with kpiwko while designing the api for SHRINKWRAP-325. > Should be able to include/exclude any main/test class/resource/webapp-resource. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-62) MavenImporter should support shrinkwrap filtering

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-62?page=com.atlassian.jira.plug... ] Andrew Rubinger commented on SHRINKRES-62: ------------------------------------------ Using the plexus-utils makes sense to me here; we're not adding an additional runtime dependency to bring it in and it satisfies your new test cases. > MavenImporter should support shrinkwrap filtering > ------------------------------------------------- > > Key: SHRINKRES-62 > URL: https://issues.jboss.org/browse/SHRINKRES-62 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven > Reporter: Karel Piwko > Assignee: Bernard Labno > Priority: Minor > Fix For: 2.0.0-beta-3 > > > Discussed with kpiwko while designing the api for SHRINKWRAP-325. > Should be able to include/exclude any main/test class/resource/webapp-resource. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-62) MavenImporter should support shrinkwrap filtering

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-62?page=com.atlassian.jira.plug... ] Andrew Rubinger updated SHRINKRES-62: ------------------------------------- Status: Resolved (was: Pull Request Sent) Labels: (was: api-change) Fix Version/s: 2.0.0-beta-3 Resolution: Done Upstream: https://github.com/shrinkwrap/resolver/commit/9849c92e80b75ec40a18683e94c... > MavenImporter should support shrinkwrap filtering > ------------------------------------------------- > > Key: SHRINKRES-62 > URL: https://issues.jboss.org/browse/SHRINKRES-62 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven > Reporter: Karel Piwko > Assignee: Bernard Labno > Priority: Minor > Fix For: 2.0.0-beta-3 > > > Discussed with kpiwko while designing the api for SHRINKWRAP-325. > Should be able to include/exclude any main/test class/resource/webapp-resource. -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues February 2013