2016-09-30 12 views
1

Ich bin Tring, um die artifactory-maven-plugin zu verwenden, um eine Maven-Build zu meinem Artefakt-Server hochladen. Das Hochladen mit dem jfrog cli funktioniert, es scheint also kein Berechtigungsproblem zu sein. Hier ist mein pom.xml:Artifactory Maven-Plugin kann nicht bereitgestellt

 <plugin> 
      <groupId>org.jfrog.buildinfo</groupId> 
      <artifactId>artifactory-maven-plugin</artifactId> 
      <version>2.6.1</version> 
      <inherited>false</inherited> 
      <executions> 
       <execution> 
        <id>build-info</id> 
        <goals> 
         <goal>publish</goal> 
        </goals> 
        <configuration> 
         <deployProperties> 
          <gradle>awesome</gradle> 
          <review.team>qa</review.team> 
         </deployProperties> 
         <contextUrl>http://vserver1.craftwater.de:8081/artifactory</contextUrl> 
         <username>myUser</username>       
         <password>mySecret</password> 
         <excludePatterns>*-tests.jar</excludePatterns> 
         <repoKey>libs-release-local</repoKey> 
         <snapshotRepoKey>libs-snapshot-local</snapshotRepoKey> 
        </configuration> 
       </execution> 
      </executions> 
     </plugin> 

Das Ergebnis mvn deploy ist ein IllegalArgutementException:

Caused by: java.lang.IllegalArgumentException: Target repository cannot be empty 
at org.jfrog.build.client.DeployDetails$Builder.build(DeployDetails.java:119) 
at org.jfrog.build.extractor.maven.BuildInfoRecorder.addDeployableArtifact(BuildInfoRecorder.java:604) 
at org.jfrog.build.extractor.maven.BuildInfoRecorder.addArtifactsToCurrentModule(BuildInfoRecorder.java:533) 
at org.jfrog.build.extractor.maven.BuildInfoRecorder.addFilesToCurrentModule(BuildInfoRecorder.java:477) 
at org.jfrog.build.extractor.maven.BuildInfoRecorder.finalizeAndAddModule(BuildInfoRecorder.java:464) 
at org.jfrog.build.extractor.maven.BuildInfoRecorder.finalizeModule(BuildInfoRecorder.java:392) 
at org.jfrog.build.extractor.maven.BuildInfoRecorder.projectSucceeded(BuildInfoRecorder.java:210) 
at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:74) 
at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) 
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:91) 
... 16 more 

Ist das ein Bug oder mache ich etwas falsch gemacht?

Artifactory Version: Artifactory OSS 4.11.1 rev 40241

Antwort

Verwandte Themen