Giovds opened a new pull request #14:
URL: https://github.com/apache/maven-gpg-plugin/pull/14
The command `mvn verify assembly:single gpg:sign` creates signed artifacts.
It places the signed artifact alongside the original as long as the original
artifact is stored in the project build directory.
However, if the original artifact is not stored in the project build
directory, and depending on the `ascDirectory` (alias `outputDirectory`) in the
pom configuration of the GPG plugin, this results in unexpected behaviour. For
example, setting the `ascDirectory` to `target/tarball` results in the
following directory structure `/path/to/project/target/gpg/target/tarball/`.
This PR resolves the issue by checking whether the root directory - relative
to the artifact - has been found and mostly adds integration tests to document
this behaviour.
---
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MGPG-44) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[MGPG-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MGPG-XXX` with the appropriate JIRA issue. Best
practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [x] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [x] You have run the integration tests successfully (`mvn -Prun-its clean
verify`).
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
