Uploaded image for project: 'Maven GPG Plugin'
  1. Maven GPG Plugin
  2. MGPG-44

gpg:sign does not handle non-Default outputDirectory correctly

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:

      Description

      The command:

      mvn verify assembly:single gpg:sign

      works fine; it creates the assemblies under target and adds the sigs to target.

      However, if the assembly plugin outputDirectory parameter is used to change the location of the assemblies - e.g. to target/tarballs - the sigs are still created, but they are left in the directory target/gpg/target/tarballs instead of being moved alongside the assemblies.

      It looks like the plugin is prefixing target/ on the ascDirectory when it should not, because defining ascDirectory=. fixes the issue

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                sebb Sebb
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: