March 2014 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-140. --------------------------------- > Update Aether implementation to org.eclipse.aether one > ------------------------------------------------------ > > Key: SHRINKRES-140 > URL: https://issues.jboss.org/browse/SHRINKRES-140 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-5 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.1.0 > > > Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version. > Update should not affect user at all, it should comprise of replacing imports with new ones. -- 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-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 closed SHRINKRES-5. ------------------------------- > 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 > Components: api-maven > Affects Versions: 2.0.2 > Reporter: Jason Porter > Priority: Minor > Labels: api-change > Fix For: 2.1.0 > > > 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-173) Configuration methods don't affect pom.xml resolution

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-173?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-173. --------------------------------- > Configuration methods don't affect pom.xml resolution > ----------------------------------------------------- > > Key: SHRINKRES-173 > URL: https://issues.jboss.org/browse/SHRINKRES-173 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: api-maven, impl-maven > Affects Versions: 2.0.2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: 2.1.0 > > > Maven Resolver allows to control resolution via following methods: > * withCentralRepo(...) > * offline(...) > * withRemoteRepo(...) > * withClasspathResolution(...) > However, with an exception of offline(...) call, all these method can be called in phase where pom.xml resolution was already done if user call loadPomFrom* method. > This means for example that resolver will touch Maven Central to resolve dependencies in pom.xml file user is loading. > In order to fix that, these methods should be callable only in configureResolver() phase, before pom.xml is touched. -- 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-164) Support encoding property from Maven compiler plugin

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-164?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-164. --------------------------------- > Support encoding property from Maven compiler plugin > ---------------------------------------------------- > > Key: SHRINKRES-164 > URL: https://issues.jboss.org/browse/SHRINKRES-164 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Affects Versions: 2.0.2 > Reporter: Thilo Mezger > Assignee: Karel Piwko > Fix For: 2.1.0 > > > I'd like to suggest that org.jboss.shrinkwrap.resolver.impl.maven.archive.plugins.CompilerPluginConfiguration should support the "encoding" property of the maven-compiler-plugin just like it supports "source" and "target". > I know that you can use "compilerArgs" to pass any parameter but that wouldn't be obvious when you have this special "encoding" parameter in maven-compiler-plugin. Everyone would expect that this setting is passed on. > And things can really go wrong in all magic ways if you compile your files with the wrong encoding... -- 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-163) Implements importTestBuildOutput for type JAR

by Johan Evelönn (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-163?page=com.atlassian.jira.plu... ] Johan Evelönn commented on SHRINKRES-163: ----------------------------------------- Sorry for the late reply. Yeah, that's exactly what i thought. Dependencies and filtering the same as importBuildOutput(). > Implements importTestBuildOutput for type JAR > --------------------------------------------- > > Key: SHRINKRES-163 > URL: https://issues.jboss.org/browse/SHRINKRES-163 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.0.2 > Reporter: Karel Piwko > > While default use case - merging src/main and src/test together might not be seen as useful, there is at least an option that user will be willing to import src/test only. > That said, implementing importTestBuildOutput() for a archive of type jar is a valid operation. -- 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-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 commented on SHRINKRES-5: ------------------------------------- Done by marcanpilami. Thank for the contribution! > 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 > Components: api-maven > Affects Versions: 2.0.2 > Reporter: Jason Porter > Priority: Minor > Labels: api-change > Fix For: 2.1.0 > > > 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

10 years, 1 month

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 resolved SHRINKRES-5. --------------------------------- Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/bf15d38d5b213b0c781d1fa06cf... > 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 > Components: api-maven > Affects Versions: 2.0.2 > Reporter: Jason Porter > Priority: Minor > Labels: api-change > Fix For: 2.1.0 > > > 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-173) Configuration methods don't affect pom.xml resolution

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-173?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-173. ----------------------------------- Resolution: Done Pushed upstream at https://github.com/shrinkwrap/resolver/commit/16809f87dd80f2a906665f0ef98.... Moved configuration related calls to configureResolver() * old methods were kept in place but @Deprecated * offline() is now workOffline(), offline() is deprecated - I had to rename method * configureFrom* methods were deprecated in favor of from* methods present on Factory, as there were called much more frequently * ConfiguredResolvedSystemFactory was dropped as it was not flexible to be called for subclasses So, user does not have to change anything in his tests, although we modified API we are fully API backwards compatible with previous release. > Configuration methods don't affect pom.xml resolution > ----------------------------------------------------- > > Key: SHRINKRES-173 > URL: https://issues.jboss.org/browse/SHRINKRES-173 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: api-maven, impl-maven > Affects Versions: 2.0.2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: 2.1.0 > > > Maven Resolver allows to control resolution via following methods: > * withCentralRepo(...) > * offline(...) > * withRemoteRepo(...) > * withClasspathResolution(...) > However, with an exception of offline(...) call, all these method can be called in phase where pom.xml resolution was already done if user call loadPomFrom* method. > This means for example that resolver will touch Maven Central to resolve dependencies in pom.xml file user is loading. > In order to fix that, these methods should be callable only in configureResolver() phase, before pom.xml is touched. -- 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-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 commented on SHRINKRES-5: ------------------------------------- API would be moved to configureResolver() resulting object, due to concerns expressed in linked issue. > 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 > Components: api-maven > Affects Versions: 2.0.2 > Reporter: Jason Porter > Priority: Minor > Labels: api-change > Fix For: 2.1.0 > > > 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-173) Configuration methods don't affect pom.xml resolution

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-173: ------------------------------------- Summary: Configuration methods don't affect pom.xml resolution Key: SHRINKRES-173 URL: https://issues.jboss.org/browse/SHRINKRES-173 Project: ShrinkWrap Resolvers Issue Type: Bug Components: api-maven, impl-maven Affects Versions: 2.0.2 Reporter: Karel Piwko Assignee: Karel Piwko Priority: Critical Fix For: 2.1.0 Maven Resolver allows to control resolution via following methods: * withCentralRepo(...) * offline(...) * withRemoteRepo(...) * withClasspathResolution(...) However, with an exception of offline(...) call, all these method can be called in phase where pom.xml resolution was already done if user call loadPomFrom* method. This means for example that resolver will touch Maven Central to resolve dependencies in pom.xml file user is loading. In order to fix that, these methods should be callable only in configureResolver() phase, before pom.xml is touched. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues March 2014