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

Karel Piwko (JIRA) issues at jboss.org
Fri Jul 4 06:05:24 EDT 2014


    [ https://issues.jboss.org/browse/SHRINKRES-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982320#comment-12982320 ] 

Karel Piwko commented on SHRINKRES-184:
---------------------------------------

This is caused by different Aether model in SWR 2.0.x and SWR 2.1.x. Same affects users migrating from Maven 3.0 to 3.1+.
Please try to define system property  -Dmaven.legacyLocalRepo=true and let me know if that fixes your issue.

> 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
>      Security Level: Public(Everyone can see) 
>         Environment: Maven 3.2.1 
> Java 7 64 - bit
> Windows 7 64 bit
>            Reporter: Sueleyman Vurucu
>
> 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.2.6#6264)


More information about the shrinkwrap-issues mailing list