January 2013 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-105) Support resolution of variables in Maven settings file

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-105: ---------------------------------- Component/s: impl-maven > Support resolution of variables in Maven settings file > ------------------------------------------------------ > > Key: SHRINKRES-105 > URL: https://issues.jboss.org/browse/SHRINKRES-105 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Reporter: Thomas SEGISMONT > Labels: maven, resolver > > Variables in Maven settings file are not resolved. > For instance if you have this node in your settings : > {code:xml} > <localRepository>${user.home}/.m2/repository</localRepository> > {code} > then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-105) Support resolution of variables in Maven settings file

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-105: ---------------------------------- Affects Version/s: 2.0.0-alpha-6 > Support resolution of variables in Maven settings file > ------------------------------------------------------ > > Key: SHRINKRES-105 > URL: https://issues.jboss.org/browse/SHRINKRES-105 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 2.0.0-alpha-6 > Reporter: Thomas SEGISMONT > Labels: maven, resolver > > Variables in Maven settings file are not resolved. > For instance if you have this node in your settings : > {code:xml} > <localRepository>${user.home}/.m2/repository</localRepository> > {code} > then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-439) Support resolution of variables in Maven settings file

by Thomas SEGISMONT (JIRA)

Thomas SEGISMONT created SHRINKWRAP-439: ------------------------------------------- Summary: Support resolution of variables in Maven settings file Key: SHRINKWRAP-439 URL: https://issues.jboss.org/browse/SHRINKWRAP-439 Project: ShrinkWrap Issue Type: Enhancement Reporter: Thomas SEGISMONT Variables in Maven settings file are not resolved. For instance if you have this node in your settings : {code:xml} <localRepository>${user.home}/.m2/repository</localRepository> {code} then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-77) Align functionality from MavenResolutionFilter with Aether DependencyFilter

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-77?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-77: --------------------------------- Labels: api-change (was: ) > Align functionality from MavenResolutionFilter with Aether DependencyFilter > --------------------------------------------------------------------------- > > Key: SHRINKRES-77 > URL: https://issues.jboss.org/browse/SHRINKRES-77 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven > Affects Versions: 2.0.0-alpha-4 > Reporter: Karel Piwko > Assignee: Andrew Rubinger > Labels: api-change > > Aether is able to filter based on path to the parent of dependency resolution. This is handy in order to create a filter which could filter based on level-nesting of the dependency itself, which is useful for lazy loading dependencies. > We need to be able to pass List<DependencyNode> parents equivalent to the filter. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-97) Allow MavenImporter to be configured

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-97?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-97: --------------------------------- Labels: api-change (was: ) > Allow MavenImporter to be configured > ------------------------------------ > > Key: SHRINKRES-97 > URL: https://issues.jboss.org/browse/SHRINKRES-97 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Karel Piwko > Labels: api-change > > Current SHRINKRES-61 implementation does not allow passing settings.xml. This is an API change and therefore must hit an alpha stream. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-5) Make it easier to add a maven repository with the maven resolvers

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-5?page=com.atlassian.jira.plugi... ] Karel Piwko updated SHRINKRES-5: -------------------------------- Labels: api-change (was: ) > Make it easier to add a maven repository with the maven resolvers > ----------------------------------------------------------------- > > Key: SHRINKRES-5 > URL: https://issues.jboss.org/browse/SHRINKRES-5 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Reporter: Jason Porter > Priority: Minor > Labels: api-change > > It should be easier to add a repository than creating a full settings.xml. Perhaps something like addRepository(String), or addRepositories(String...) -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-44) ShrinkRes 1.0.0-X: Update Aether to 1.13.1

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-44?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-44: --------------------------------- Summary: ShrinkRes 1.0.0-X: Update Aether to 1.13.1 (was: Update Aether to 1.13.1) > ShrinkRes 1.0.0-X: Update Aether to 1.13.1 > ------------------------------------------ > > Key: SHRINKRES-44 > URL: https://issues.jboss.org/browse/SHRINKRES-44 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 1.0.0-beta-7 > Reporter: Karel Piwko > Assignee: Karel Piwko > > Aether should be updated to the latest version, as it was done in upstream. > This will make packaging of ShrinkWrap Maven resolver in Fedora much easier. > Due to Aether Maven repository changes, a fix for Maven Repository types is required ( > https://gist.github.com/1362504): > {code} > aused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:156) > ... 48 more > Caused by: java.lang.RuntimeException: Could not create new descriptor instance > at org.jboss.shrinkwrap.resolver.api.DependencyBuilderInstantiator.createFromUserView(DependencyBuilderInstantiator.java:101) > at org.jboss.shrinkwrap.resolver.api.DependencyResolvers.use(DependencyResolvers.java:39) > at org.scalabox.lift.helloworld.HelloWorldTest$.deployment(HelloWorldTest.scala:93) > at org.scalabox.lift.helloworld.HelloWorldTest.deployment(HelloWorldTest.scala) > ... 53 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at org.jboss.shrinkwrap.resolver.api.DependencyBuilderInstantiator.createFromUserView(DependencyBuilderInstantiator.java:96) > ... 56 more > Caused by: java.lang.IllegalArgumentException: No manager available for local repository /Users/g/.m2/repository of type enhanced using the available factories EnhancedLocalRepositoryManagerFactory, SimpleLocalRepositoryManagerFactory > at org.sonatype.aether.impl.internal.DefaultRepositorySystem.newLocalRepositoryManager(DefaultRepositorySystem.java:454) > at org.jboss.shrinkwrap.resolver.impl.maven.MavenManagerBuilder.localRepositoryManager(MavenManagerBuilder.java:106) > at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.getSession(MavenRepositorySystem.java:79) > at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.<init>(MavenBuilderImpl.java:110) > ... 61 more > Caused by: org.sonatype.aether.repository.NoLocalRepositoryManagerException: No manager available for local repository /Users/g/.m2/repository of type enhanced using the available factories EnhancedLocalRepositoryManagerFactory, SimpleLocalRepositoryManagerFactory > at org.sonatype.aether.impl.internal.DefaultLocalRepositoryProvider.newLocalRepositoryManager(DefaultLocalRepositoryProvider.java:139) > at org.sonatype.aether.impl.internal.DefaultRepositorySystem.newLocalRepositoryManager(DefaultRepositorySystem.java:450) > {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

13 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 updated SHRINKRES-62: --------------------------------- Labels: api-change (was: ) > 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 > Priority: Minor > Labels: api-change > > 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

13 years, 2 months

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-100?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-100: ---------------------------------- Labels: api-change (was: ) > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-18) MavenImporter on war files should support a configuration that supports "skipping the build" in the IDE (and preferably use it by default)

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-18?page=com.atlassian.jira.plug... ] Karel Piwko resolved SHRINKRES-18. ---------------------------------- Fix Version/s: 2.0.0-alpha-7 Resolution: Done > MavenImporter on war files should support a configuration that supports "skipping the build" in the IDE (and preferably use it by default) > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: SHRINKRES-18 > URL: https://issues.jboss.org/browse/SHRINKRES-18 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Affects Versions: 2.0.0-alpha-1 > Reporter: Geoffrey De Smet > Assignee: Karel Piwko > Fix For: 2.0.0-alpha-7 > > > Currently the MavenImporter on war files requires "mvn package" to be run every time (not only the first time), to update the exploded directory at "target/{finalName}". > This means if you change something in your code and want to (re)run a test, > and forget to run "mvn package" first, you're running the old code (and the results are not representative of the changed code). > Karel and Geoffrey discussed this at JUDCon London. > The following things can be probably presumed: > - The IDE compiles all classes from src/main/java to target/classes. > - The IDE copies all non-filtered resources from src/main/resources to target/classes. > - That target/classes is copied into the war at WEB-INF/classes. > - Most src/main/webapp dirs are copied unaltered into the root of the war. (*) > - "mvn compile" is run once after any "mvn clean": in other words, all src/main/filtered-resources are in target/classes > So MavenImporter doesn't have to require "mvn package" to build the exploded dir first (which it then zips, enriches and sends to arquillian). > Instead, it can construct the war zip directly from target/classes and src/main/webapp. > That is at least one less copy and more importantly, to run the test from the IDE without having to build first. > Note: all examples above used the explicit directory locations, but in reality the pom.xml's <build> section should be used to determinate the directory locations for a certain project. -- 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

13 years, 2 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 January 2013