Fix potential NPE in Maven publication

A Maven publication does not always have a main artifact. Issue jfrog#247
ljacomet · Oct 16, 2019 · 5e5b187 · 5e5b187
1 parent 04e8afd
commit 5e5b187
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/...c/main/groovy/org/jfrog/gradle/plugin/artifactory/task/helper/TaskHelperPublications.java b/...c/main/groovy/org/jfrog/gradle/plugin/artifactory/task/helper/TaskHelperPublications.java
@@ -248,8 +248,10 @@ public Set<GradleDeployDetails> getArtifactDeployDetails() {
                     addMavenArtifactToDeployDetails(deployDetails, publicationName, builder, artifactInfo, mavenPublication);
                 }
             }
-            // Second adding the main artifact of the publication
-            createPublishArtifactInfoAndAddToDeployDetails(mavenNormalizedPublication.getMainArtifact(), deployDetails, mavenPublication, publicationName);
+            // Second adding the main artifact of the publication, if present
+            if (mavenNormalizedPublication.getMainArtifact() != null) {
+                createPublishArtifactInfoAndAddToDeployDetails(mavenNormalizedPublication.getMainArtifact(), deployDetails, mavenPublication, publicationName);
+            }
 
             // Third adding all additional artifacts - includes Gradle Module Metadata when produced
             Set<MavenArtifact> artifacts = mavenNormalizedPublication.getAdditionalArtifacts();