March 2014 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKWRAP-453) Paths in webarchives are not calculated correctly

by Pawan Dubey (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-453?page=com.atlassian.jira.pl... ] Pawan Dubey commented on SHRINKWRAP-453: ---------------------------------------- [~kpiwko] Can we just not use Pattern.quote() here inside String.replaceFirst() to send the literal interpretation of the string instead of translating it as regex? > Paths in webarchives are not calculated correctly > ------------------------------------------------- > > Key: SHRINKWRAP-453 > URL: https://issues.jboss.org/browse/SHRINKWRAP-453 > Project: ShrinkWrap > Issue Type: Bug > Components: api > Affects Versions: 1.1.2 > Environment: Win7x64, JDK1.7.0_17x32, JBOSS 7.1.3.Final, Arquillian 1.0.3Final, JUnit 4.11 > Reporter: Stefan Hösel > > When creating a WebArchive via ShrinkWrap from a directory that is an exploded war file, paths inside this archive (generated with "arquillian.xml/arquillian/engine/property[deploymentExportPath]->target/deployments") generated invalid in some cases. > When investigating the sources I found "org.jboss.shrinkwrap.impl.base.importer.ExplodedImporterImpl.calculatePath(File root, File child)" uses "String.replaceFirst" to replace the occurance of rootPath in childPath to create a local war file path. My path of the directory that needs compression contains *brackets*, which (as well as other path elements, e.g. ".") are interpreted as regular expression tokens and therefore don't match. > The resulting archive can not be delpoyed in AS and tests can not be performed automatically. > The code to create the WebArchive looks like this: > {{ShrinkWrap._create_(WebArchive.{color:gray}*class*{color}, resultingWarFileNameAsString)}} > {{.as(ExplodedImporter.{color:gray}*class*{color}).importDirectory(absolutePathToExplodedWarDirectoryAsFile)}} > {{.as(WebArchive.{color:gray}*class*{color});}} -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-172) Unable to go offline() in MavenImporter

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-172?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-172. ----------------------------------- Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/4c60f30138885d16f6b11c4dbfb... > Unable to go offline() in MavenImporter > --------------------------------------- > > Key: SHRINKRES-172 > URL: https://issues.jboss.org/browse/SHRINKRES-172 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: api-maven > Affects Versions: 2.0.2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.1.0 > > > Unable to call offline() on MavenImporter, e.g. > {code} > ShrinkWrap.create(MavenImporter.class).offline().loadPomFromFile(AG_PUSH_POM_XML_LOCATION).importBuildOutput() > .as(WebArchive.class); > {code} > It is possible only if you pass settings.xml first -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-478) Wrong exception message if no service was found

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-478?page=com.atlassian.jira.pl... ] Karel Piwko updated SHRINKWRAP-478: ----------------------------------- Labels: starter (was: ) > Wrong exception message if no service was found > ----------------------------------------------- > > Key: SHRINKWRAP-478 > URL: https://issues.jboss.org/browse/SHRINKWRAP-478 > Project: ShrinkWrap > Issue Type: Bug > Components: spi > Affects Versions: 1.2.1 > Reporter: Karel Piwko > Labels: starter > > If there is no service available, SWR complains there is more then one service available: > https://github.com/shrinkwrap/resolver/blob/master/spi/src/main/java/org/... -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-478) Wrong exception message if no service was found

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-478?page=com.atlassian.jira.pl... ] Karel Piwko updated SHRINKWRAP-478: ----------------------------------- Assignee: (was: Karel Piwko) > Wrong exception message if no service was found > ----------------------------------------------- > > Key: SHRINKWRAP-478 > URL: https://issues.jboss.org/browse/SHRINKWRAP-478 > Project: ShrinkWrap > Issue Type: Bug > Components: spi > Affects Versions: 1.2.1 > Reporter: Karel Piwko > > If there is no service available, SWR complains there is more then one service available: > https://github.com/shrinkwrap/resolver/blob/master/spi/src/main/java/org/... -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-478) Wrong exception message if no service was found

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-478?page=com.atlassian.jira.pl... ] Karel Piwko updated SHRINKWRAP-478: ----------------------------------- Component/s: spi (was: api) > Wrong exception message if no service was found > ----------------------------------------------- > > Key: SHRINKWRAP-478 > URL: https://issues.jboss.org/browse/SHRINKWRAP-478 > Project: ShrinkWrap > Issue Type: Bug > Components: spi > Affects Versions: 1.2.1 > Reporter: Karel Piwko > Assignee: Karel Piwko > > If there is no service available, SWR complains there is more then one service available: > https://github.com/shrinkwrap/resolver/blob/master/spi/src/main/java/org/... -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-478) Wrong exception message if no service was found

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-478?page=com.atlassian.jira.pl... ] Karel Piwko moved SHRINKRES-171 to SHRINKWRAP-478: -------------------------------------------------- Project: ShrinkWrap (was: ShrinkWrap Resolvers) Key: SHRINKWRAP-478 (was: SHRINKRES-171) Issue Type: Bug (was: Enhancement) Affects Version/s: 1.2.1 (was: 2.0.2) Component/s: api (was: api) Fix Version/s: (was: 2.1.0) > Wrong exception message if no service was found > ----------------------------------------------- > > Key: SHRINKWRAP-478 > URL: https://issues.jboss.org/browse/SHRINKWRAP-478 > Project: ShrinkWrap > Issue Type: Bug > Components: api > Affects Versions: 1.2.1 > Reporter: Karel Piwko > Assignee: Karel Piwko > > If there is no service available, SWR complains there is more then one service available: > https://github.com/shrinkwrap/resolver/blob/master/spi/src/main/java/org/... -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-172) Unable to go offline() in MavenImporter

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-172: ------------------------------------- Summary: Unable to go offline() in MavenImporter Key: SHRINKRES-172 URL: https://issues.jboss.org/browse/SHRINKRES-172 Project: ShrinkWrap Resolvers Issue Type: Bug Components: api-maven Affects Versions: 2.0.2 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 2.1.0 Unable to call offline() on MavenImporter, e.g. {code} ShrinkWrap.create(MavenImporter.class).offline().loadPomFromFile(AG_PUSH_POM_XML_LOCATION).importBuildOutput() .as(WebArchive.class); {code} It is possible only if you pass settings.xml first -- 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-151) Descriptors should generate a common parent for different spec versions

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-151?page=com.atlassian.jira.pl... ] George Gastaldi updated SHRINKDESC-151: --------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/shrinkwrap/descriptors/pull/96 > Descriptors should generate a common parent for different spec versions > ----------------------------------------------------------------------- > > Key: SHRINKDESC-151 > URL: https://issues.jboss.org/browse/SHRINKDESC-151 > Project: ShrinkWrap Descriptors > Issue Type: Feature Request > Components: api-javaee > Reporter: George Gastaldi > Assignee: Ralf Battenfeld > > This affects only the JavaEE API. Some usecases manipulate descriptors regardless of the version it is currently on. The API could be abstracted to a common interface so that common element types to the supported complex types could be used. > A sample is provided in https://github.com/forge/javaee-descriptors/. The IMPL remains untouched (as generated by the ShrinkWrap generator) and common types are refactored to a super interface: > Super Interface: https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > Sub Interfaces: > https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > The generated code doesn't need to change either. The existence of the super interface is what matters most. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-151) Descriptors should generate a common parent for different spec versions

by Ralf Battenfeld (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-151?page=com.atlassian.jira.pl... ] Ralf Battenfeld commented on SHRINKDESC-151: -------------------------------------------- Thanks George. I will cleanup and finalize this. > Descriptors should generate a common parent for different spec versions > ----------------------------------------------------------------------- > > Key: SHRINKDESC-151 > URL: https://issues.jboss.org/browse/SHRINKDESC-151 > Project: ShrinkWrap Descriptors > Issue Type: Feature Request > Components: api-javaee > Reporter: George Gastaldi > Assignee: Ralf Battenfeld > > This affects only the JavaEE API. Some usecases manipulate descriptors regardless of the version it is currently on. The API could be abstracted to a common interface so that common element types to the supported complex types could be used. > A sample is provided in https://github.com/forge/javaee-descriptors/. The IMPL remains untouched (as generated by the ShrinkWrap generator) and common types are refactored to a super interface: > Super Interface: https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > Sub Interfaces: > https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > The generated code doesn't need to change either. The existence of the super interface is what matters most. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-171) Wrong exception message if no service was found

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-171: ------------------------------------- Summary: Wrong exception message if no service was found Key: SHRINKRES-171 URL: https://issues.jboss.org/browse/SHRINKRES-171 Project: ShrinkWrap Resolvers Issue Type: Enhancement Components: api Affects Versions: 2.0.2 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 2.1.0 If there is no service available, SWR complains there is more then one service available: https://github.com/shrinkwrap/resolver/blob/master/spi/src/main/java/org/... -- 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

10 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 March 2014