gnodet opened a new pull request, #408: URL: https://github.com/apache/maven-filtering/pull/408
## Summary Implements the feature requested in [MRESOURCES-162](https://github.com/apache/maven-resources-plugin/issues/400): a configurable option to fail the build when a filter expression cannot be resolved, instead of silently passing the placeholder through to the output. ## Changes - **`AbstractMavenFilteringRequest`**: add `failOnMissingFilterValue` boolean (default `false`, backward compatible) - **`MavenResourcesExecution.copyOf()`**: propagate the new field - **`BaseFilter.Wrapper`**: thread the flag to the filter reader - **`InterpolatorFilterReaderLineEnding`**: throw `IOException` on unresolved token when enabled - **`MultiDelimiterInterpolatorFilterReaderLineEnding`**: same ## Behaviour When `failOnMissingFilterValue` is `false` (default): existing behaviour unchanged — unresolved `${placeholder}` is passed through as-is. When `failOnMissingFilterValue` is `true`: any placeholder that no `ValueSource` can resolve throws an `IOException` with a message identifying the token (e.g. `Unresolved filter token: '${missing.property}'`). This propagates through `FilteringUtils` → `DefaultMavenFileFilter` → `DefaultMavenResourcesFiltering` → `MavenFilteringException`, causing a build failure. ## Next step A follow-up PR to `apache/maven-resources-plugin` will expose this as a `@Parameter(property="maven.resources.failOnMissingFilterValue")` on the Mojo. -- 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]
