Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry-pick #3034: [BEAM-2242] Ensure that jars are shaded correctly by running the jar plugin before the shade plugin #3061

Closed
wants to merge 1 commit into from

Conversation

lukecwik
Copy link
Member

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.

…plugin before the shade plugin

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.
asfgit pushed a commit that referenced this pull request May 10, 2017
@dhalperi
Copy link
Contributor

LGTM as faithful cherry pick and merged.

@lukecwik lukecwik closed this May 10, 2017
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 4324d9d on lukecwik:beam2242 into ** on apache:release-2.0.0**.

@lukecwik lukecwik deleted the beam2242 branch September 26, 2017 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants