gnodet commented on issue #471: URL: https://github.com/apache/maven-resources-plugin/issues/471#issuecomment-5804499639
This was fixed by bumping `maven-filtering` to 3.5.1 in commit 1f8a00efce93353684031e20f7d754821059d37f. The root cause was a regression introduced in `maven-filtering` 3.3.2 that broke the "first `<resource>` entry wins" semantics for overlapping resource declarations. It was fixed in [`maven-filtering` 3.5.1](https://github.com/apache/maven-filtering/releases/tag/maven-filtering-3.5.1) (see apache/maven-filtering#333 and apache/maven-filtering#334). The fix will be included in the upcoming `maven-resources-plugin` 3.5.1 release. In the meantime, you can work around it by adding an explicit dependency on `maven-filtering` 3.5.1 in the plugin's `<dependencies>` block. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
