gnodet commented on issue #273: URL: https://github.com/apache/maven-resources-plugin/issues/273#issuecomment-5832080168
Closing this as Won't Fix. Resource directories are intentionally optional by design — this is what allows profiles, generated sources, and OS-specific resources to work without every declared directory needing to exist in every environment. If you need to enforce that a specific file or directory exists before the build proceeds, the Maven Enforcer Plugin's [`requireFilesExist`](https://maven.apache.org/enforcer/enforcer-rules/requireFilesExist.html) rule is the right tool for that — it is purpose-built for this kind of precondition check and keeps the concern separate from the resource copying step. Adding a `mandatory` flag to resource declarations would be an API change across maven-filtering and the plugin for a use case that is already covered by existing tooling. -- 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]
