August 2014 - shrinkwrap-issues - Jboss List Archives

[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 reassigned SHRINKRES-165: ------------------------------------- Assignee: Karel Piwko (was: Andrew Rubinger) > Honor maven.legacyLocalRepo property > ------------------------------------ > > Key: SHRINKRES-165 > URL: https://issues.jboss.org/browse/SHRINKRES-165 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: impl-maven > Affects Versions: 2.0.2 > Reporter: Karel Piwko > Assignee: Karel Piwko > > 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.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-58) Customizable properties in MavenDependencyResolver

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-58?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-58: --------------------------------- Assignee: (was: Andrew Rubinger) > Customizable properties in MavenDependencyResolver > -------------------------------------------------- > > Key: SHRINKRES-58 > URL: https://issues.jboss.org/browse/SHRINKRES-58 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Josef Cacek > > PicketLink integration testsuite uses MavenDependencyResolver to resolve test dependencies, but we need to customize properties when we're testing. > For instance we use sed to edit <version.picketlink> in pom.xml for now. It would be much more handy if we are able to provide customized properties to MavenDependency resolver and handle configuration without such hacks. > c.f. > our usage of the MavenDependencyResolver: > https://github.com/picketlink/picketlink-integration-tests/blob/master/un... > parent/pom.xml in which version.picketlink is defined > https://github.com/picketlink/picketlink-integration-tests/blob/master/pa... > pom.xml for PicketLink integration tests (adds version.picketlink as system property to failsafe tests) > https://github.com/picketlink/picketlink-integration-tests/blob/master/in... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-149) Maven classpathworkspace resolver shouldn't assume classes are under target/classes

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-149?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-149: ---------------------------------- Assignee: (was: Andrew Rubinger) > Maven classpathworkspace resolver shouldn't assume classes are under target/classes > ----------------------------------------------------------------------------------- > > Key: SHRINKRES-149 > URL: https://issues.jboss.org/browse/SHRINKRES-149 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0 > Reporter: Matthieu Baechler > > To avoid conflicting builds between Maven and Eclipse, I put eclipse build into a "eclipse-build/classes" directory. > Considering this configuration, with the following code : > {code:java} > Maven.resolver() > .offline() > .loadPomFromFile("../../pom.xml") > .resolve("com.linagora.obm:services-module:2.6.0-SNAPSHOT") > .withClassPathResolution(true) > .withTransitivity() > .asFile(); > {code} > Maven resolver find my services-module on the classpath, but when trying a build a jar, it fails in MavenResolvedArtifactImpl.artifactToFile : > {code:java} > // SHRINKRES-102, allow test classes to be packaged as well > File root = new File(artifact.getFile().getParentFile(), "target/classes"); > {code} > In my case, target/classes contains maven build result and not what's on the classpath. > Can this resolver use the classes on the classpath instead ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-126) Support for p2 repositories

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-126?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-126: ---------------------------------- Assignee: (was: Andrew Rubinger) > Support for p2 repositories > --------------------------- > > Key: SHRINKRES-126 > URL: https://issues.jboss.org/browse/SHRINKRES-126 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Michal Matloka > > [~gastaldi] has sent me an issue they had with aether in Forge > saying we might have similiar problem in SWR: FORGE-866 > https://github.com/forge/core/commit/7acb9217bdff22ed0084fd853002d3e466a9... > According to [~kpiwko] usage with p2 repositories was never tested. > Support for p2 repositires probably needs to be verified. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-180) transitive dependencies updated from provided to compile

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-180?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-180: ---------------------------------- Assignee: (was: Andrew Rubinger) > transitive dependencies updated from provided to compile > -------------------------------------------------------- > > Key: SHRINKRES-180 > URL: https://issues.jboss.org/browse/SHRINKRES-180 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0-alpha-2 > Reporter: Markus Schulz > Fix For: 2.2.0-alpha-3 > > Attachments: deptree.txt, MavenResolverTest.java, transitivetest-pom.xml > > > i have a pom with something like: > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-search</artifactId> > <version>4.2.0.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-core</artifactId> > <scope>provided</scope> > </dependency> > hibernate-search internally dependes on hibernate-core (scope compile). But in don't want to get hbernate-core in my deployment, therefore it's forced to provided. > But: > File[] testLibs = Maven.configureResolver() > .workOffline() > .loadPomFromClassLoaderResource("transitivetest-pom.xml") > .importRuntimeDependencies() > .resolve() > .withTransitivity() > .asFile(); > still contains hibernate-core.jar -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-128) Improve JavaDocs of methods taking coordinate in canonical form

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-128?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-128: ---------------------------------- Assignee: (was: Andrew Rubinger) > Improve JavaDocs of methods taking coordinate in canonical form > --------------------------------------------------------------- > > Key: SHRINKRES-128 > URL: https://issues.jboss.org/browse/SHRINKRES-128 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Michal Matloka > Priority: Minor > > Descriptions in exception and internal classes was improved in SHRINKRES-113. It appears that some API methods JavaDocs still needs improvements. See last post in forum reference. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-150) Wrong built WebArchive using Shrinkwrap Classpath resolution

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-150?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-150: ---------------------------------- Assignee: (was: Andrew Rubinger) > Wrong built WebArchive using Shrinkwrap Classpath resolution > ------------------------------------------------------------ > > Key: SHRINKRES-150 > URL: https://issues.jboss.org/browse/SHRINKRES-150 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0 > Environment: win 7 (64 bit), glassfish 3.1.2 > Reporter: Gunther Klein > > Hi, > I have defined a simple war project and setup an arquillian test using shrinkwrap 2.0.0, that - as a test - just resolves the web archive via classpath resolution: > {code:borderStyle=solid} > @RunWith(Arquillian.class) > public class ShrinkwrapTestIT { > @Deployment > public static Archive<?> createDeployment() { > WebArchive war = Maven.resolver() > .resolve("shrinkwrap.test:shrinkwrap.test:war:0.0.1-SNAPSHOT").withClassPathResolution(true) > .withoutTransitivity().asSingle(WebArchive.class); > System.out.println(war.toString(true)); > return war; > } > @Test > public void test() { > //do nothing > } > } > {code} > The output shows, that the archive is incomplete (resource files are missing) and not even war conform: > some_text_file.txt > com/ > com/test/ > com/test/Test.class > If i change the code to use .withClassPathResolution(false), the output is: > /some_text_file.txt > /index.jsp > /com/ > /com/test/ > /com/test/Test.class > /WEB-INF/ > /WEB-INF/web.xml > /WEB-INF/sun-web.xml > /META-INF/ > /META-INF/MANIFEST.MF > > Now the resources are included, but the class(es) are packaged at the top level and not under /WEB-INF/classes, so it still doesnt respresent a valid war. My pom looks like: > {code:xml} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>shrinkwrap.test</groupId> > <artifactId>shrinkwrap.test</artifactId> > <version>0.0.1-SNAPSHOT</version> > <packaging>war</packaging> > <properties> > <project.build.sourceEncoding>ISO8859-1</project.build.sourceEncoding> > <version.shrinkwrap.resolvers>2.0.0</version.shrinkwrap.resolvers> > </properties> > <dependencies> >  > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <version>4.11</version> > </dependency> > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-container</artifactId> > <scope>test</scope> > </dependency> > <dependency> > <groupId>org.jboss.arquillian.container</groupId> > <artifactId>arquillian-glassfish-remote-3.1</artifactId> > <version>1.0.0.CR4</version> > <scope>test</scope> > </dependency> > <dependency> > <groupId>org.jboss.shrinkwrap.resolver</groupId> > <artifactId>shrinkwrap-resolver-depchain</artifactId> > <version>${version.shrinkwrap.resolvers}</version> > <scope>test</scope> > <type>pom</type> > </dependency> > </dependencies> > <dependencyManagement> > <dependencies> >  > <dependency> > <groupId>org.jboss.shrinkwrap.resolver</groupId> > <artifactId>shrinkwrap-resolver-bom</artifactId> > <version>${version.shrinkwrap.resolvers}</version> > <scope>import</scope> > <type>pom</type> > </dependency> > <dependency> > <groupId>org.jboss.arquillian</groupId> > <artifactId>arquillian-bom</artifactId> > <version>1.1.1.Final</version> > <scope>import</scope> > <type>pom</type> > </dependency> > </dependencies> > </dependencyManagement> > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-failsafe-plugin</artifactId> > <version>2.16</version> > <configuration> > <skipTests>${skipITs}</skipTests> > </configuration> > <executions> > <execution> > <goals> > <goal>integration-test</goal> > <goal>verify</goal> > </goals> > </execution> > </executions> > </plugin> > </plugins> > </build> > </project> > {code} > Why is shrinkwrap giving me corrupt archives here in both cases? For the case with classpath resolution i would expect shrinkwrap to give me the war, that was built by maven in the package phase? Without classpath resolution i would expect shrinkwrap to resolve the war from maven respository (local or remote). Or is my understanding of shrinkwrap (classpath) resolution wrong here? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-181) MavenArtifactInfo is missing <optional> info

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-181?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-181: ---------------------------------- Assignee: (was: Andrew Rubinger) > MavenArtifactInfo is missing <optional> info > -------------------------------------------- > > Key: SHRINKRES-181 > URL: https://issues.jboss.org/browse/SHRINKRES-181 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: api-maven > Affects Versions: 2.2.0-alpha-2 > Reporter: Ales Justin > Fix For: 2.2.0-alpha-3 > > > There is no way to tell if MavenArtifactInfo is optional, > if not using custom strategy. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-131) Align property name in between Maven Plugin and rest of ShrinkRes

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-131?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-131: ---------------------------------- Assignee: (was: Andrew Rubinger) > Align property name in between Maven Plugin and rest of ShrinkRes > ----------------------------------------------------------------- > > Key: SHRINKRES-131 > URL: https://issues.jboss.org/browse/SHRINKRES-131 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: maven-plugin > Reporter: Karel Piwko > Priority: Minor > > Maven plugin should be using the same property names as the rest of the ShrinkWrap Maven Resolver. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-179) Build Fails in JDK8

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-179?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-179. ----------------------------------- Fix Version/s: 2.2.0-alpha-3 Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/1238c27a81d718772bc0fe983f8... > Build Fails in JDK8 > ------------------- > > Key: SHRINKRES-179 > URL: https://issues.jboss.org/browse/SHRINKRES-179 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0-alpha-2 > Reporter: Andrew Rubinger > Assignee: Karel Piwko > Fix For: 2.2.0-alpha-3 > > > In environment: > {code}alr@distortion ~/business/jboss/git/shrinkwrap/resolver $ mvn -version > Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T12:37:52-05:00) > Maven home: /usr/local/Cellar/maven/3.2.1/libexec > Java version: 1.8.0_05, vendor: Oracle Corporation > Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"{code} > The build fails due to: > {code}[INFO] Running post-build script: /Users/alr/business/jboss/git/shrinkwrap/resolver/maven-plugin/target/it/dependency-tree-scope/verify.bsh > [INFO] Finished post-build script: /Users/alr/business/jboss/git/shrinkwrap/resolver/maven-plugin/target/it/dependency-tree-scope/verify.bsh > [INFO] ..SUCCESS (1.4 s) > [INFO] ------------------------------------------------- > [INFO] Build Summary: > [INFO] Passed: 3, Failed: 1, Errors: 0, Skipped: 0 > [INFO] ------------------------------------------------- > [ERROR] The following builds failed: > [ERROR] * dependency-tree/pom.xml{code} > Available in the logs: > https://shrinkwrap.ci.cloudbees.com/view/SWR/job/ShrinkWrap_Resolver_upst... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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 August 2014