Uploaded image for project: 'Forge'
  1. Forge
  2. FORGE-1134

Forge fails to resolve dependencies in password protected Maven repositories

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 1.4.1.Final
    • 1.4.0.Final
    • Build Tools - Maven
    • None

      Given a password protected repository defined in settings.xml, like:

      ...
          <server>
              <id>central</id>
              <username>testuser</username>
              <password>testuser123</password></server>
          </servers>
      ...
          <profiles>
              <profile>
                  <id>nexus</id>
                  <activation>
                      <activeByDefault>true</activeByDefault>
                  </activation>
                  <repositories>
                      <repository>
                          <id>central</id>
                          <url>http://localhost:8081/nexus/content/repositories/central/</url>
                          <releases>
                              <enabled>true</enabled>
                          </releases>
                          <snapshots>
                              <enabled>true</enabled>
                          </snapshots>
                      </repository>
                  </repositories>
                  <pluginRepositories>
                      <pluginRepository>
                          <id>central</id>
                          <url>http://localhost:8081/nexus/content/repositories/central/</url>
                          <releases>
                              <enabled>true</enabled>
                          </releases>
                          <snapshots>
                              <enabled>true</enabled>
                          </snapshots>
                      </pluginRepository>
                  </pluginRepositories>
              </profile>
          </profiles>
      

      Forge fails to resolve artifacts, since it does not take the passwords into consideration when attempting to resolve the artifacts, resulting in an error like so (with the fix for FORGE-1133) :

      [no project] vineet $ forge install-plugin arquillian
      ***INFO*** Preparing to install plugin: arquillian
      ***INFO*** Checking out plugin source files to [/tmp/forgetemp6567964705967228540] via 'git'
      ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
      ***WARNING*** Failed to read artifact descriptor for org.apache.velocity:velocity:jar:1.7
      ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final
      ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final
      ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final
      ***WARNING*** Failed to read artifact descriptor for org.sonatype.aether:aether-api:jar:1.11
      ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final
      ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final
      ***WARNING*** Failed to read artifact descriptor for org.codehaus.jackson:jackson-core-asl:jar:1.9.1
      ***WARNING*** Failed to read artifact descriptor for org.codehaus.jackson:jackson-mapper-asl:jar:1.9.1
      ***WARNING*** Failed to read artifact descriptor for junit:junit:jar:4.8.2
       ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] 
      ***INFO*** Cleaning up temp workspace [/tmp/forgetemp6567964705967228540]
      Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
      Deleted /tmp/forgetemp6567964705967228540
      ***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces)
      

              vineet.reynolds_jira Vineet Reynolds (Inactive)
              vineet.reynolds_jira Vineet Reynolds (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: