September 2014 - shrinkwrap-issues

[JBoss JIRA] (SHRINKRES-73) Improve error message for unsupported type of dependency

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-73?page=com.atlassian.jira.plug... ] Karel Piwko closed SHRINKRES-73. -------------------------------- > Improve error message for unsupported type of dependency > -------------------------------------------------------- > > Key: SHRINKRES-73 > URL: https://issues.jboss.org/browse/SHRINKRES-73 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Affects Versions: 2.0.0-alpha-4 > Reporter: Karel Piwko > Fix For: 2.2.0-beta-1 > > > <dependency> declaration might contain a type which is not valid at given place, such as import. > We should definitely make exception message better if that happens. > {code} > IllegalArgumentException : Packaging type import is not supported > {code} > As a side note, type can be virtually anything, I'm not sure if we can provide a typesafe enum here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-165) Honor maven.legacyLocalRepo property

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-165?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-165. --------------------------------- > Honor maven.legacyLocalRepo property > ------------------------------------ > > Key: SHRINKRES-165 > URL: https://issues.jboss.org/browse/SHRINKRES-165 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: maven > Affects Versions: 2.0.2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.2.0-beta-1 > > > Since Maven 3.1.0, there is a possibility to disable tracking of remote repositories for artifacts available in local repository > {code} > maven.legacyLocalRepo > {code} > ShrinkWrap Resolvers should honor this property. > Additionally, there could be a top level API that allows to do the same. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-204) Broken filtering of archives via MavenImporter on Windows

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-204?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-204. --------------------------------- > Broken filtering of archives via MavenImporter on Windows > --------------------------------------------------------- > > Key: SHRINKRES-204 > URL: https://issues.jboss.org/browse/SHRINKRES-204 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-alpha-2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.2.0-beta-1 > > Attachments: org.jboss.shrinkwrap.resolver.impl.maven.archive.importer.ConfiguredMavenImporterTestCase.txt, org.jboss.shrinkwrap.resolver.impl.maven.archive.importer.JarMavenImporterTestCase.txt, org.jboss.shrinkwrap.resolver.impl.maven.archive.importer.WarMavenImporterTestCase.txt > > > MavenImporter ignores resource filtering - inclusions are not a part of resulting archives on Windows platform. > It is unclear whether this is a bug in implementation or in test bed. To be investigated. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-194) Multi-module gradle project support

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-194?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-194. --------------------------------- > Multi-module gradle project support > ----------------------------------- > > Key: SHRINKRES-194 > URL: https://issues.jboss.org/browse/SHRINKRES-194 > Project: ShrinkWrap Resolvers > Issue Type: Sub-requirement > Components: gradle > Affects Versions: 2.2.0-alpha-2 > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 2.2.0-beta-1 > > > Issue from github https://github.com/mmatloka/arquillian-gradle-sample/issues/1: > {quote} > Hi, > I'm very glad for your gradle resolver. However, we have multi project setup in which this code fails with an ArrayIndexOutOfBoundException > {code} > final GradleProject gradleProject = projectConnection.getModel(GradleProject.class); > final File buildDir = new File(projectDir, "build"); > final File libsDir = new File(buildDir, "libs"); > final File result = libsDir.listFiles(new FilenameFilter() { > @Override > public boolean accept(final File dir, final String name) { > return name.startsWith(gradleProject.getName()); > } > })[0]; > {code} > This is imho due to the fact that the gradleProject above holds the multi project but the arquillian tests are contained (and should be contained) in the sub project (*server). There the predicate will never be true and the [0] with end up in an exception. > I think you can either do a deep search to also get the sub project jars or more accurately resolve the project the tests are in. If you need help let me know. > Best, > Maik > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-196) FormatStage should work in a JDK8 friendly way

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-196?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-196. --------------------------------- > FormatStage should work in a JDK8 friendly way > ---------------------------------------------- > > Key: SHRINKRES-196 > URL: https://issues.jboss.org/browse/SHRINKRES-196 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api, maven > Affects Versions: 2.2.0-alpha-1, 2.2.0-alpha-2 > Reporter: John Ament > Assignee: John Ament > Labels: api-change > Fix For: 2.2.0-beta-1 > > > Currently, FormatStage only returns arrays. In JDK8 if I want to stream the results to merge JARs, I have to do this: > JavaArchive jar = ShrinkWrap.create(JavaArchive.class, "se-examples.jar").addPackage(UndertowComponent.class.getPackage()) > .addPackage(ExampleConfigSource.class.getPackage()).addPackage(GreeterServlet.class.getPackage()) > .addAsManifestResource(new StringAsset(beansXml),"beans.xml"); > Arrays.stream(Maven.resolver().loadPomFromFile("pom.xml") > .resolve("org.apache.deltaspike.core:deltaspike-core-api","org.apache.deltaspike.core:deltaspike-core-impl") > .withTransitivity().as(JavaArchive.class)).forEach(jar::merge); > The Arrays.stream here is ugly as sin, requires me to wrap the result. It would be better if there was an asList(Class<?>) method that did the appropriate type conversion and returned as a list of whatevers. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 closed SHRINKRES-176. --------------------------------- > MavenImporter archive name > -------------------------- > > Key: SHRINKRES-176 > URL: https://issues.jboss.org/browse/SHRINKRES-176 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Reporter: Michael Irwin > Assignee: Karel Piwko > Fix For: 2.2.0-beta-1 > > > 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)

11 years, 6 months

1
0
0 / 0

[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 closed SHRINKRES-187. --------------------------------- > ParsedPomFile does not expose test resources > -------------------------------------------- > > Key: SHRINKRES-187 > URL: https://issues.jboss.org/browse/SHRINKRES-187 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: maven > Affects Versions: 2.0.2 > Reporter: Falko M. > Assignee: Karel Piwko > Labels: api-change > Fix For: 2.2.0-beta-1 > > > 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)

11 years, 6 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 closed SHRINKRES-198. --------------------------------- > 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: maven > Affects Versions: 2.1.1 > Reporter: Tako Schotanus > Assignee: Karel Piwko > Priority: Minor > Fix For: 2.2.0-beta-1 > > > 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)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-202) withClassPathResolution method in ConfigurableMavenResolverSystemImpl ignores parameter

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-202?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-202. --------------------------------- > withClassPathResolution method in ConfigurableMavenResolverSystemImpl ignores parameter > --------------------------------------------------------------------------------------- > > Key: SHRINKRES-202 > URL: https://issues.jboss.org/browse/SHRINKRES-202 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.1.1 > Reporter: Daniele Gaffuri > Assignee: Karel Piwko > Priority: Minor > Labels: starter > Fix For: 2.2.0-beta-1 > > > The implementation of withClassPathResolution in org.jboss.shrinkwrap.resolver.impl.maven.ConfigurableMavenResolverSystemImpl ignores its parameter and always disables resolution > {code} > public ConfigurableMavenResolverSystem withClassPathResolution(boolean useClassPathResolution) { > getMavenWorkingSession().disableClassPathWorkspaceReader(); > return this; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-195) activeProfiles element from settings.xml seems to be ignored, property override not working

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-195?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-195. --------------------------------- > activeProfiles element from settings.xml seems to be ignored, property override not working > ------------------------------------------------------------------------------------------- > > Key: SHRINKRES-195 > URL: https://issues.jboss.org/browse/SHRINKRES-195 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.0.2 > Environment: Win7 x64 > JDK7u51 > Reporter: Falko M. > Assignee: Karel Piwko > Priority: Minor > Fix For: 2.2.0-beta-1 > > > See: > http://maven.apache.org/settings.html#Active_Profiles > On the command line (mvn), the element is evaluated as expected and the specified profiles are activated but when I load the very same pom.xml via {{Maven.resolver().offline().loadPomFromFile(...)}}, the respective profiles are ignored, as it seems. > I came accross this issue when I wanted to override a property from pom.xml in settings.xml and {{ParsedPomFile.getProperties()}} kept returning the non-overriden value. > Notes: > - the following in settings.xml *does work*: > {noformat} > <activation> > <activeByDefault>true</activeByDefault> > </activation> > {noformat} > - a new property defined in a settings.xml profile also doesn't show up in {{ParsedPomFile.getProperties()}} which seems to prove that the profile is not actived -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 September 2014