You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2017/05/19 17:44:04 UTC
[jira] [Resolved] (BEAM-2252) maven-shade-plugin should be defined
in pluginManagement instead of plugins so that the plugin execution order
defined by the root pom.xml is used
[ https://issues.apache.org/jira/browse/BEAM-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Cwik resolved BEAM-2252.
-----------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
> maven-shade-plugin should be defined in pluginManagement instead of plugins so that the plugin execution order defined by the root pom.xml is used
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-2252
> URL: https://issues.apache.org/jira/browse/BEAM-2252
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow, runner-direct, sdk-java-core, sdk-java-gcp
> Affects Versions: 2.1.0
> Reporter: Luke Cwik
> Assignee: Luke Cwik
> Priority: Minor
> Labels: newbie, starter
> Fix For: 2.1.0
>
>
> Several of our child pom.xml declare maven-shade-plugin within build/plugins instead of build/pluginManagement which affects the plugin execution order.
> See BEAM-2242 for when we surgically fixed how shading was performed and this issue is about revisiting that change and improving upon it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)