[GLASSFISH-18224] Not able to deploy to maven.java.net due to invalid signature Created: 19/Jan/12  Updated: 19/Jan/12  Resolved: 19/Jan/12

Status: Resolved
Project: glassfish
Component/s: None
Affects Version/s: 3.1.2_b17
Fix Version/s: 3.1.2_b19

Type: Bug Priority: Major
Reporter: janey Assignee: sirajg
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1_2-approved

 Description   

An ant task is added during install phase that repackages the war artifact in the module admingui/war and it's causing invalid gpg signature when deploying to maven.java.net repo.
-Invalid Signature: '/org/glassfish/main/admingui/war/3.1.2-b17/war-3.1.2-b17.war.asc' is not a valid signature for 'war-3.1.2-b17.war'.

Artifacts are now signed during verify phase when deploying to maven.java.net repository.

The fix is to change "install" phase to "packaging" phase.



 Comments   
Comment by scatari [ 19/Jan/12 ]

Approved as this is required for deployment to maven.java.net.

Comment by sirajg [ 19/Jan/12 ]

Diffs :

— pom.xml (revision 52204)
+++ pom.xml (working copy)
@@ -62,7 +62,7 @@
<version>2.0.2</version>
<executions>
<execution>

  • <phase>install</phase>
    + <phase>package</phase>
    <configuration>
    <archive>
    <manifestEntries>
    @@ -79,7 +79,7 @@
    <artifactId>maven-antrun-plugin</artifactId>
    <executions>
    <execution>
  • <phase>install</phase>
    + <phase>package</phase>
    <configuration>
Generated at Sun Apr 19 02:18:03 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.