You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2019/12/25 19:33:37 UTC
[GitHub] [maven-shade-plugin] peterdemaeyer opened a new pull request #34:
[MSHADE-340] - Shaded test jar artifact is not attached to the project
peterdemaeyer opened a new pull request #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project
URL: https://github.com/apache/maven-shade-plugin/pull/34
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/MSHADE) 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 `[MSHADE-XXX] - Fixes bug in ApproximateQuantiles`,
where you replace `MSHADE-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)
- [x] 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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [maven-shade-plugin] khmarbaise closed pull request #34:
[MSHADE-340] - Shaded test jar artifact is not attached to the project
Posted by GitBox <gi...@apache.org>.
khmarbaise closed pull request #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project
URL: https://github.com/apache/maven-shade-plugin/pull/34
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [maven-shade-plugin] peterdemaeyer commented on issue #34:
[MSHADE-340] - Shaded test jar artifact is not attached to the project
Posted by GitBox <gi...@apache.org>.
peterdemaeyer commented on issue #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project
URL: https://github.com/apache/maven-shade-plugin/pull/34#issuecomment-568925286
Fixed {{ShadeMojo}} such that the shaded test JAR is attached to the project also when {{shadedArtifactAttached=true}}.
Integration test added illustrating scenario, fails without fix and succeeds with the fix.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [maven-shade-plugin] khmarbaise commented on issue #34:
[MSHADE-340] - Shaded test jar artifact is not attached to the project
Posted by GitBox <gi...@apache.org>.
khmarbaise commented on issue #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project
URL: https://github.com/apache/maven-shade-plugin/pull/34#issuecomment-570819272
Run of CI was successful. Merged into master. Thanks for your contribution.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [maven-shade-plugin] khmarbaise commented on issue #34:
[MSHADE-340] - Shaded test jar artifact is not attached to the project
Posted by GitBox <gi...@apache.org>.
khmarbaise commented on issue #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project
URL: https://github.com/apache/maven-shade-plugin/pull/34#issuecomment-570818048
Let's see what CI says...
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services