Maven 2.x and 3.x GPG Plugin

With maven 2.1.0 some poms end up with invalid signatures

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.0-alpha-4
  • Fix Version/s: 1.0
  • Component/s: None
  • Labels:
    None
  • Patch Submitted:
    Yes
  • Number of attachments :
    2

Description

The pom-transformed.xml is installed, but gpg is signing the original pom.xml. Thus, the signature is invalid.

  1. patch.txt
    05/May/09 10:24 AM
    5 kB
    Daniel Kulp
  2. patch2.txt
    05/May/09 10:55 AM
    6 kB
    Daniel Kulp

Issue Links

Activity

Hide
Daniel Kulp added a comment -

The attached patch seems to work fine for Maven 2.1.0 and 2.0.9. However, there is a little bit of "hackish" code in there that's I'd like some others to look at before I commit it.

Show
Daniel Kulp added a comment - The attached patch seems to work fine for Maven 2.1.0 and 2.0.9. However, there is a little bit of "hackish" code in there that's I'd like some others to look at before I commit it.
Hide
Daniel Kulp added a comment -


New version of patch with comments to explain some of the hacks

Show
Daniel Kulp added a comment - New version of patch with comments to explain some of the hacks
Hide
John Casey added a comment -

This has been fixed in Maven core for the 2.2.0 release, so a fix here is redundant.

Show
John Casey added a comment - This has been fixed in Maven core for the 2.2.0 release, so a fix here is redundant.
Hide
Daniel Kulp added a comment -

Is the fix to the maven core being back ported for maven 2.1.1? If not, then a fix here may be needed.

Show
Daniel Kulp added a comment - Is the fix to the maven core being back ported for maven 2.1.1? If not, then a fix here may be needed.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: