[jira] [Commented] (MSHADE-434) Strange side-effect on rat-plugin

["Christofer Dutz (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MSHADE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881646#comment-17881646 ] 

Christofer Dutz commented on MSHADE-434:
----------------------------------------

I can confirm the same behaviour in the Apache PLC4X build. Here we are stuck at 
maven-shade-plugin as updating to anything above 3.2.4 causes the rat plugin to complain about stuff in the target directory as soon as the shade plugin is being used.

> Strange side-effect on rat-plugin
> ---------------------------------
>
>                 Key: MSHADE-434
>                 URL: https://issues.apache.org/jira/browse/MSHADE-434
>             Project: Maven Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>            Reporter: Chesnay Schepler
>            Priority: Major
>
> When upgrading the shade-plugin from 3.2.4 to 3.3.0, without changing anything else, the Apache Flink builds are getting failed by the rat-plugin, complaining about a number of files in the root target/ directory.
> These files do exist, but are usually excluded by the plugin.
> For some reason upgrading the shade-plugin is changing this behavior.
> {code:java}
> [WARNING] Files with unapproved licenses:
>   /home/chesnay/dev/repos/flink/flink/target/rat.txt
>   /home/chesnay/dev/repos/flink/flink/target/checkstyle-result.xml
>   /home/chesnay/dev/repos/flink/flink/target/checkstyle-cachefile
> {code}
> This is reeeeally strange, and were wondering if you guys have any ideas for what could going on here.
> Interestingly enough explicitly listing these files (e.g., {{**/rat.txt}}) results in them being excluded again.
> This happened with Java 8 + Maven 3.2.5 and Java 11 + Maven 3.8.6 and is 100% reproducible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)