rzo1 opened a new issue, #333:
URL: https://github.com/apache/maven-filtering/issues/333
### Affected versions
`maven-filtering` 3.3.2 and later (3.3.2, 3.4.0, 3.5.0). Last known-good:
3.3.1.
### Summary
When a single source directory is covered by **two `<resource>` entries** —
one with `filtering=true` plus a narrow `<include>`, the other with
`filtering=false` plus `<include>**</include>` — the file selected by the
first entry is no longer filtered. The placeholder is left as the literal
`${...}` text instead of being replaced.
This was first reported downstream against `maven-resources-plugin` in
[apache/maven-resources-plugin#471][mrp-471]. Bisecting the
`maven-resources-plugin` history shows the regression entered with
[`493aa46`][mrp-bump], a one-line dependency bump from
`maven-filtering` 3.3.1 → 3.3.2, with no source change in the plugin itself.
The root cause therefore lives here, in `maven-filtering`.
### Reproducer
A self-contained JUnit test that exercises `MavenResourcesFiltering`
directly is available on a branch:
<https://github.com/rzo1/maven-filtering/tree/mrp-471-overlapping-resources-repro>
[mrp-471]: https://github.com/apache/maven-resources-plugin/issues/471
[mrp-bump]:
https://github.com/apache/maven-resources-plugin/commit/493aa4642e11aa92724330af85785f7939688793
--
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]
