August 2015 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-228) Re-enable maven integration tests module

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-228: ------------------------------------- Summary: Re-enable maven integration tests module Key: SHRINKRES-228 URL: https://issues.jboss.org/browse/SHRINKRES-228 Project: ShrinkWrap Resolvers Issue Type: Task Components: maven Reporter: Karel Piwko Assignee: Matous Jobanek Fix For: 3.0.0 Re-enable Maven integration tests module in pom.xml aggregator file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-226) Loading of the settings.xml configuration should be postponed

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-226?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-226: ---------------------------------- Fix Version/s: 2.2.0 (was: 2.2.0-beta-3) > Loading of the settings.xml configuration should be postponed > ------------------------------------------------------------- > > Key: SHRINKRES-226 > URL: https://issues.jboss.org/browse/SHRINKRES-226 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: maven > Affects Versions: 2.2.0-beta-2 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.0 > > > Currently when the Maven.configureResolver() is called, the default settings.xml is immediately loaded - this is not always appropriate - see: https://developer.jboss.org/message/936418 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-224) Generated artifacts from workspace are missing directory entries

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-224?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-224: ---------------------------------- Fix Version/s: 2.2.0 (was: 2.2.0-beta-3) > Generated artifacts from workspace are missing directory entries > ---------------------------------------------------------------- > > Key: SHRINKRES-224 > URL: https://issues.jboss.org/browse/SHRINKRES-224 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-beta-2 > Reporter: Karel Piwko > Fix For: 2.2.0 > > > In order to able to use spring annotations "component-scan" to bind classes the external jar files HAVE TO contains directory entries. If these entries are not present the automatic scan is not working. > In current version, the zip file build from a workspace project included in arquillian deployment does not contains this entries. > For more infos : http://stackoverflow.com/questions/1242656/spring-annotation-based-contro... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-214) NoResolvedResultException when trying to resolve a POM

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-214: ------------------------------------- Fix Version/s: 3.0.0 (was: 2.2.0-beta-3) > NoResolvedResultException when trying to resolve a POM > ------------------------------------------------------ > > Key: SHRINKRES-214 > URL: https://issues.jboss.org/browse/SHRINKRES-214 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-beta-1 > Reporter: Michael Schnell > Fix For: 3.0.0 > > > Trying to resolve a "pom" results in an org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to resolve dependencies, none of them were found. > Looking at the local Maven repository, the POM was actually loaded from the remote repo, but it's not returned: > {code:java} > Maven.resolver().resolve("org.jboss:jboss-parent:pom:12").withoutTransitivity().asSingleFile(); > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-210) Dependency management with scopes are not resolved correctly

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-210?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-210: ------------------------------------- Fix Version/s: 3.0.0 > Dependency management with scopes are not resolved correctly > ------------------------------------------------------------ > > Key: SHRINKRES-210 > URL: https://issues.jboss.org/browse/SHRINKRES-210 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-beta-1 > Reporter: Emond Papegaaij > Fix For: 3.0.0 > > > If the scope of an indirect dependency is changed in the dependencyManagement of your pom, this scope is not correctly taken into account when resolving compileAndRuntimeDependencies. I've created a very minimal testcase to demonstrate this problem: > https://github.com/papegaaij/resolve-dep > This testcase resolves the dependencies using: > {code} > File[] jars = Maven.configureResolver().workOffline() > .loadPomFromFile("pom.xml") > .importCompileAndRuntimeDependencies().resolve() > .withTransitivity().as(File.class); > {code} > The pom only defines 1 compile dependency (shrinkwrap-impl-base), which depends on 2 others (shrinkwrap-api and shrinkwrap-spi). shrinkwrap-api has a dependencyManagement with scope provided, so I expect this resolution to yield 2 files (base and spi), but it yields all 3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-199) SWR, Stop searching in other repositories, if it finds the artifact at first.

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-199?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-199: ------------------------------------- Fix Version/s: 3.0.0 (was: 2.2.0-beta-3) > SWR, Stop searching in other repositories, if it finds the artifact at first. > ----------------------------------------------------------------------------- > > Key: SHRINKRES-199 > URL: https://issues.jboss.org/browse/SHRINKRES-199 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: maven > Reporter: Srinivas Akula > Fix For: 3.0.0 > > > Shrinkwraps Resolver always look into all the repositories > configured in POM/settings.xml including http://repo1.maven.org/maven/ even though it found the artifact and it waits for time out there. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-208) Add option to set connection timeout

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-208?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-208: ------------------------------------- Fix Version/s: 3.1.0 (was: 2.2.0-beta-3) > Add option to set connection timeout > ------------------------------------ > > Key: SHRINKRES-208 > URL: https://issues.jboss.org/browse/SHRINKRES-208 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Reporter: Tako Schotanus > Priority: Minor > Fix For: 3.1.0 > > > As discussed on this Ceylon issue https://github.com/ceylon/ceylon-module-resolver/issues/80 we'd like to have the ability to set the connection timeout for Aether resolving so we have a consistent timeout setting across our connectivity options. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-193) Allow resolving only poms without downloading artifacts themselves

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-193?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-193: ------------------------------------- Fix Version/s: 3.0.0 (was: 2.2.0-beta-3) > Allow resolving only poms without downloading artifacts themselves > ------------------------------------------------------------------ > > Key: SHRINKRES-193 > URL: https://issues.jboss.org/browse/SHRINKRES-193 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: maven > Affects Versions: 2.1.1 > Reporter: Binod Pant > Fix For: 3.0.0 > > > See https://community.jboss.org/message/884084#884084 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-191) Refactor project structure - gradle and maven separation

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-191?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-191: ------------------------------------- Fix Version/s: 3.0.0 > Refactor project structure - gradle and maven separation > -------------------------------------------------------- > > Key: SHRINKRES-191 > URL: https://issues.jboss.org/browse/SHRINKRES-191 > Project: ShrinkWrap Resolvers > Issue Type: Task > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 3.0.0 > > > Currently SWR structure contains all modules in main project directory. I propose to seperate maven and gradle modules into seperate subdirectories. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-188) Support installation of an artifact to a local repository

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-188?page=com.atlassian.jira.plu... ] Matous Jobanek closed SHRINKRES-188. ------------------------------------ Resolution: Won't Fix Please use Arquillian Spacelift to install artifacts into your local repository > Support installation of an artifact to a local repository > --------------------------------------------------------- > > Key: SHRINKRES-188 > URL: https://issues.jboss.org/browse/SHRINKRES-188 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: maven > Affects Versions: 2.2.0-alpha-2 > Reporter: Tomas Rohovsky > > It would be a nice feature to provide installation of an artifact to a local repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 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 August 2015