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

[Karel Piwko (JIRA)]

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

Karel Piwko edited comment on SHRINKRES-184 at 7/29/14 6:52 AM:
----------------------------------------------------------------

Arquillian version should be unrelated, it just maintains Resolver version. We are looking for a regression for your test case in SWR 2.0.2 and 2.1.0, since Arquillian 1.1.4.Final 2.1.x is the stream we are using.

Just to check whether I'm on the right path, can you search your local repository for "_remote.repositories" files for artifacts you are trying to resolved and delete these files?


was (Author: kpiwko):
Arquillian version should be unrelated, it just maintains Resolver version. We are looking for a regression for your test case in SWR 2.0.2 and 2.1.0.

Just to check whether I'm on the right path, can you search your local repository for "_remote.repositories" files for artifacts you are trying to resolved and delete these files?

> 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)