beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Cwik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (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
Date Wed, 10 May 2017 21:46:04 GMT

     [ https://issues.apache.org/jira/browse/BEAM-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Luke Cwik updated BEAM-2252:
----------------------------
    Labels: newbie starter  (was: )

> 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
>            Priority: Minor
>              Labels: newbie, starter
>
> 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)

Mime
View raw message