September 2014 - shrinkwrap-issues

[JBoss JIRA] (SHRINKRES-187) ParsedPomFile does not expose test resources

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-187?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-187. ----------------------------------- Assignee: Karel Piwko Resolution: Done Landed in https://github.com/shrinkwrap/resolver/commit/79c624ae1b4ebaae441c6adfdac... > ParsedPomFile does not expose test resources > -------------------------------------------- > > Key: SHRINKRES-187 > URL: https://issues.jboss.org/browse/SHRINKRES-187 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: api-maven > Affects Versions: 2.0.2 > Reporter: Falko M. > Assignee: Karel Piwko > Labels: api-change > Fix For: 2.2.0-alpha-3 > > > There is {{ParsedPomFile.getResources()}} but this does not include test resouces and there is no {{.getTestResources()}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-176) MavenImporter archive name

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-176?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-176. ----------------------------------- Resolution: Done Landed in https://github.com/shrinkwrap/resolver/commit/b7da0660d0470d994d3a88fdf13... > MavenImporter archive name > -------------------------- > > Key: SHRINKRES-176 > URL: https://issues.jboss.org/browse/SHRINKRES-176 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Reporter: Michael Irwin > Assignee: Karel Piwko > Fix For: 2.2.0-alpha-3 > > > When using the MavenImporter, the archiveName property is ignored. > {code} > WebArchive archive = ShrinkWrap.create(MavenImporter.class, "test.war") > .loadPomFromFile("pom.xml") > .importBuildOutput() > .as(WebArchive.class); > System.out.println(archive.getName()); > {code} > The archive name will be whatever the name of the Maven artifact is, which is usually [artifactId]-[version]. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-197) Use settings.security property to get settings-security.xml location

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-197?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-197. ----------------------------------- Resolution: Done Landed in https://github.com/shrinkwrap/resolver/commit/c0ca3e4a615129da62fadf6849b... > Use settings.security property to get settings-security.xml location > -------------------------------------------------------------------- > > Key: SHRINKRES-197 > URL: https://issues.jboss.org/browse/SHRINKRES-197 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.2.0-alpha-2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.2.0-alpha-3 > > > settings-security.xml should use -Dsettings.security property instead of current one: > See > https://jira.codehaus.org/browse/MNG-4853 > Likely we'll will keep older property there working and just remove it from documentation. > cc'ed [~wujaszek] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-197) Use settings.security property to get settings-security.xml location

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-197?page=com.atlassian.jira.plu... ] Karel Piwko reassigned SHRINKRES-197: ------------------------------------- Assignee: Karel Piwko > Use settings.security property to get settings-security.xml location > -------------------------------------------------------------------- > > Key: SHRINKRES-197 > URL: https://issues.jboss.org/browse/SHRINKRES-197 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.2.0-alpha-2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.2.0-alpha-3 > > > settings-security.xml should use -Dsettings.security property instead of current one: > See > https://jira.codehaus.org/browse/MNG-4853 > Likely we'll will keep older property there working and just remove it from documentation. > cc'ed [~wujaszek] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-198) maven.util.FileUtil contains System.out.println

by Tako Schotanus (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-198?page=com.atlassian.jira.plu... ] Tako Schotanus commented on SHRINKRES-198: ------------------------------------------ Ok thx! > maven.util.FileUtil contains System.out.println > ----------------------------------------------- > > Key: SHRINKRES-198 > URL: https://issues.jboss.org/browse/SHRINKRES-198 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.1 > Reporter: Tako Schotanus > Assignee: Karel Piwko > Priority: Minor > Fix For: 2.2.0-alpha-3 > > > Don't know if it needs more explanation than the title, but the code in org/jboss/shrinkwrap/resolver/impl/maven/util/FileUtil.java contains a call to System.out.println() which definitely shouldn't be there. > NB: I put the priority to "minor" although really it's quite annoying and definitely not suitable for us in a production environment! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-200?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-200. ----------------------------------- Assignee: Pawan Dubey Fix Version/s: 2.2.0-alpha-3 Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/d87d3854b5e089cb8663c2c9de9.... Thanks Pawan! > Wrong exception message if no service was found > ----------------------------------------------- > > Key: SHRINKRES-200 > URL: https://issues.jboss.org/browse/SHRINKRES-200 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: api > Affects Versions: 2.1.1 > Reporter: Karel Piwko > Assignee: Pawan Dubey > Labels: starter > Fix For: 2.2.0-alpha-3 > > > 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 was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-198) maven.util.FileUtil contains System.out.println

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-198?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-198: --------------------------------------- [~quintesse] I expect to have a release that will hit Maven Central at the end of this week. > maven.util.FileUtil contains System.out.println > ----------------------------------------------- > > Key: SHRINKRES-198 > URL: https://issues.jboss.org/browse/SHRINKRES-198 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.1 > Reporter: Tako Schotanus > Assignee: Karel Piwko > Priority: Minor > Fix For: 2.2.0-alpha-3 > > > Don't know if it needs more explanation than the title, but the code in org/jboss/shrinkwrap/resolver/impl/maven/util/FileUtil.java contains a call to System.out.println() which definitely shouldn't be there. > NB: I put the priority to "minor" although really it's quite annoying and definitely not suitable for us in a production environment! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-200?page=com.atlassian.jira.plu... ] Karel Piwko moved SHRINKWRAP-478 to SHRINKRES-200: -------------------------------------------------- Project: ShrinkWrap Resolvers (was: ShrinkWrap) Key: SHRINKRES-200 (was: SHRINKWRAP-478) Affects Version/s: 2.1.1 (was: 1.2.1) Component/s: api (was: spi) > Wrong exception message if no service was found > ----------------------------------------------- > > Key: SHRINKRES-200 > URL: https://issues.jboss.org/browse/SHRINKRES-200 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: api > Affects Versions: 2.1.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 was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

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

by Pawan Dubey (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-478?page=com.atlassian.jira.pl... ] Pawan Dubey commented on SHRINKWRAP-478: ---------------------------------------- [~kpiwko] https://github.com/shrinkwrap/resolver/pull/72 > 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 was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-198) maven.util.FileUtil contains System.out.println

by Tako Schotanus (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-198?page=com.atlassian.jira.plu... ] Tako Schotanus commented on SHRINKRES-198: ------------------------------------------ Ah, ok, well a -beta might do, so when would you expect to release this? (I know that date would come with a disclaimer saying you can't be held responsible for that date slipping by a year or two hehe). I just want to know if we can wait for it or if we have to think about shipping our own patched stable 2.1.1 version. > maven.util.FileUtil contains System.out.println > ----------------------------------------------- > > Key: SHRINKRES-198 > URL: https://issues.jboss.org/browse/SHRINKRES-198 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: impl-maven > Affects Versions: 2.1.1 > Reporter: Tako Schotanus > Assignee: Karel Piwko > Priority: Minor > Fix For: 2.2.0-alpha-3 > > > Don't know if it needs more explanation than the title, but the code in org/jboss/shrinkwrap/resolver/impl/maven/util/FileUtil.java contains a call to System.out.println() which definitely shouldn't be there. > NB: I put the priority to "minor" although really it's quite annoying and definitely not suitable for us in a production environment! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues September 2014