ExportXMLWordPrintable

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Major
    • Component/s: maven-plugin
    • None
    • Environment:
      Platform: Sun, OS: Solaris

      When "mvn install" runs on slaves, Hudson copies them to the local
      repository of the master.

      However, the master may need to modify the location of the local repository, by
      setting the value -Dmaven.repo.local=<repository> in the MAVEN_OPTS of the job
      configuration.

      If this is set then the "mvn install" build works fine, but during the archiving
      step the default location (~/.m2/ or /.m2) is used rather than the location
      specified by maven.repo.location. This results in an error if this location is
      non-writable - particularly a problem if the user under which tomcat is running
      has no $HOME.

      ERROR: Failed to install artifact to the master
      org.apache.maven.artifact.installer.ArtifactInstallationException:
      Error installing artifact:
      /.m2/repository/someartifact.jar(No such file or directory)
      at
      org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:84)
      at
      hudson.maven.reporters.MavenArtifactArchiver$1.call(MavenArtifactArchiver.java:93)
      at
      hudson.maven.reporters.MavenArtifactArchiver$1.call(MavenArtifactArchiver.java:76)
      at
      hudson.maven.MavenBuild$ProxyImpl.execute(MavenBuild.java:208)
      at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown
      Source)

            Assignee:
            Unassigned
            Reporter:
            stuart_owen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: