March 2015 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-116) Gradle support

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-116?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-116. ----------------------------------- Fix Version/s: 2.2.0-beta-1 Resolution: Done Marking this issues are resolved. Gradle support was delivered in various 2.2.0 releases, 2.2.0-beta-1 being the latest significant modification of the code base. > Gradle support > -------------- > > Key: SHRINKRES-116 > URL: https://issues.jboss.org/browse/SHRINKRES-116 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Affects Versions: 2.0.0-beta-2 > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 2.2.0-beta-1 > > > ShrinkWrap Resolver was designed to support multiple dependency management/build systems. It seems that there are already people using Gradle wanting to use ShrinkWrap. API seems much more friendly than Aether ;) and probably even supports build in 'build' feature. > http://forums.gradle.org/gradle/topics/dependency_resolution_with_gradle_... > http://gradle.1045684.n5.nabble.com/Gradle-support-for-Arquillian-maybe-a... > https://community.jboss.org/message/772433 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-116) Gradle support

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-116?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-116. --------------------------------- > Gradle support > -------------- > > Key: SHRINKRES-116 > URL: https://issues.jboss.org/browse/SHRINKRES-116 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Affects Versions: 2.0.0-beta-2 > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 2.2.0-beta-1 > > > ShrinkWrap Resolver was designed to support multiple dependency management/build systems. It seems that there are already people using Gradle wanting to use ShrinkWrap. API seems much more friendly than Aether ;) and probably even supports build in 'build' feature. > http://forums.gradle.org/gradle/topics/dependency_resolution_with_gradle_... > http://gradle.1045684.n5.nabble.com/Gradle-support-for-Arquillian-maybe-a... > https://community.jboss.org/message/772433 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-206) Change default build location of Embedded Gradle Importer

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-206?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-206: ---------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Out of Date This issue was made obsolete in merged PR #77 > Change default build location of Embedded Gradle Importer > --------------------------------------------------------- > > Key: SHRINKRES-206 > URL: https://issues.jboss.org/browse/SHRINKRES-206 > Project: ShrinkWrap Resolvers > Issue Type: Sub-task > Reporter: Michal Matloka > Assignee: Michal Matloka > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-206) Change default build location of Embedded Gradle Importer

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-206?page=com.atlassian.jira.plu... ] Michal Matloka commented on SHRINKRES-206: ------------------------------------------ In https://github.com/shrinkwrap/resolver/pull/75 I had doubts if this was really needed, so https://github.com/shrinkwrap/resolver/pull/77 was prepared a bit modified, but yes, we can close this. > Change default build location of Embedded Gradle Importer > --------------------------------------------------------- > > Key: SHRINKRES-206 > URL: https://issues.jboss.org/browse/SHRINKRES-206 > Project: ShrinkWrap Resolvers > Issue Type: Sub-task > Reporter: Michal Matloka > Assignee: Michal Matloka > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-193?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-193: ---------------------------------- Fix Version/s: 2.2.0-beta-3 (was: 2.2.0-cr-1) > 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: 2.2.0-beta-3 > > > See https://community.jboss.org/message/884084#884084 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-184) Shrinkwrap maven local repo resolution not working since ARQ 1.1.4.Final

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-184?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-184: ---------------------------------- Fix Version/s: 2.2.0-beta-3 (was: 2.2.0-cr-1) > Shrinkwrap maven local repo resolution not working since ARQ 1.1.4.Final > ------------------------------------------------------------------------ > > Key: SHRINKRES-184 > URL: https://issues.jboss.org/browse/SHRINKRES-184 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Environment: Maven 3.2.1 > Java 7 64 - bit > Windows 7 64 bit > Reporter: Sueleyman Vurucu > Fix For: 2.2.0-beta-3 > > > I update ARQ from 1.1.3.Final to 1.1.4.Final. > After I try to excecute my testsuite I had a Exception that some of the artifacts could not be resolved. After Debugging I see that shrinkwrap looks for that artifacts on our local nexus server. Unfortunately we dont deploy our development artifact on nexus. > The MavenResolverSystem is configured like shown below: > // ARQ 1.1.3.Final > private static MavenResolverSystem getMavenDependencyResolver() { > MavenResolverSystem mavenResolverSystem = Maven.configureResolver().fromFile(pathToSettingsXML); > mavenResolverSystem.offline(); > return mavenResolverSystem; > } > // ARQ 1.1.4.Final > private static ConfigurableMavenResolverSystem getMavenDependencyResolver() { > ConfigurableMavenResolverSystem mavenResolverSystem = Resolvers.configure(ConfigurableMavenResolverSystem.class); > mavenResolverSystem.withClassPathResolution(true); > mavenResolverSystem.fromFile(pathToSettingsXML); > mavenResolverSystem.workOffline(); > return mavenResolverSystem; > } > As you can see I say to MavenResolverSystem that it should work offline. > After deep debugging I see that the resolversystem try to find all the artifacts on our nexus. > //ARQ 1.1.3.Final > DefaultRepositorySystem:367 > com.siemag.base:wms-base-controller:ejb:3.0.0-SNAPSHOT <(compile) > //ARQ 1.1.4.Final > In the class DefaultRepositorySystem:367 > com.siemag.base:wms-base-controller:ejb:3.0.0-SNAPSHOT < [nexus (http://172.16.55.1:8081/nexus/content/groups/public, releases)] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-199?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-199: ---------------------------------- Fix Version/s: 2.2.0-beta-3 (was: 2.2.0-cr-1) > 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: 2.2.0-beta-3 > > > 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.11#6341)

9 years, 1 month

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-208?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-208: ---------------------------------- Fix Version/s: 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: 2.2.0-beta-3 > > > 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.11#6341)

9 years, 1 month

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: ---------------------------------- Fix Version/s: 2.2.0-beta-3 (was: 2.2.0-cr-1) > transitive dependencies updated from provided to compile > -------------------------------------------------------- > > Key: SHRINKRES-180 > URL: https://issues.jboss.org/browse/SHRINKRES-180 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.2.0-alpha-2 > Reporter: Markus Schulz > Fix For: 2.2.0-beta-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.3.11#6341)

9 years, 1 month

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-214: ---------------------------------- Fix Version/s: 2.2.0-beta-3 (was: 2.2.0-cr-1) > 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: 2.2.0-beta-3 > > > 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.11#6341)

9 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 2015