Sebb opened MGPG-44 and commented
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
Issue Links:
- MGPG-45 ascDirectory has no effect unless artifacts are not in target
Remote Links:
1 votes, 3 watchers
Sebb opened MGPG-44 and commented
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
Issue Links:
Remote Links:
1 votes, 3 watchers