GitHub user lukecwik opened a pull request:

    https://github.com/apache/beam/pull/3034

    [BEAM-2242] Ensure that the test jar is shaded correctly

    This required listing the maven jar plugin earlier within the file so that 
the jar/test jar ran before shade within the package phase.
    
    I also update the maven shade plugin version in archetypes to pickup the 
fixes in the service file transformer and dropped the usage of finalName in the 
shade plugin so all artifacts are named the same way.
    
    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`.
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf).
    
    ---


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/lukecwik/incubator-beam beam2242

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/3034.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3034
    
----
commit ea938d06f7f431c94d5635e9b1b885283c5cf604
Author: Luke Cwik <lc...@google.com>
Date:   2017-05-10T02:07:36Z

    [BEAM-2242] Ensure that the test jar is shaded correctly
    
    This required listing the maven jar plugin earlier within the file so that 
the jar/test jar ran before shade within the package phase.
    
    I also update the maven shade plugin version in archetypes to pickup the 
fixes in the service file transformer and dropped the usage of finalName in the 
shade plugin so all artifacts are named the same way.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to