[
https://issues.apache.org/jira/browse/FLINK-27886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-27886:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Error way for skipping shade plugin in sub-modules
> --------------------------------------------------
>
> Key: FLINK-27886
> URL: https://issues.apache.org/jira/browse/FLINK-27886
> Project: Flink
> Issue Type: Improvement
> Components: BuildSystem / Shaded
> Affects Versions: 1.13.6, 1.14.4, 1.15.0
> Reporter: Ran Tao
> Priority: Major
> Labels: pull-request-available, stale-major
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Currently in some sub-modules, for example, flink-quickstart-java
> flink-quickstart-scala, flink-walkthrough, we want to skip shade but use
> error way like this
> {code:java}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-shade-plugin</artifactId>
> <executions>
> <execution>
> </phase>
> </execution>
> </executions>
> </plugin>
> {code}
> It just set none phase for itself, can't forbid the inherited parent shade.
> !screenshot-1.png!
> !screenshot-2.png!
> the correct way is
> {code:java}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-shade-plugin</artifactId>
> <executions>
> <execution>
> <id>shade-flink</id>
> <phase>none</phase>
> </execution>
> </executions>
> </plugin>
> {code}
> it can forbid parent shade-flink and also it's own shade. because there are
> no extra own shade executions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
