Uploaded image for project: 'ShrinkWrap Resolvers'
  1. ShrinkWrap Resolvers
  2. SHRINKRES-184

Shrinkwrap maven local repo resolution not working since ARQ 1.1.4.Final

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • None

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

            Unassigned Unassigned
            suikast42 Süleyman Vurucu (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: