Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip validation/transformation when base directory does not exist #57

Open
sewe opened this issue Jul 18, 2020 · 2 comments
Open

Skip validation/transformation when base directory does not exist #57

sewe opened this issue Jul 18, 2020 · 2 comments

Comments

@sewe
Copy link

sewe commented Jul 18, 2020

At the moment, defining an <execution> of the validate or transform goals in a parent POM, meant to be reused across various child projects, is really cumbersome since is requires the <dir> configured in the <validationSet> or <transformationSet> to exist in the parent, too; Otherwise, the build fails:

The directory /tmp/parent/src/main/xml, which is a base directory of a ValidationSet or TransformationSet, does not exist.

Would it be possible to implement a Skip non-existing base directory behavior, either optionally or even as a default? This would mirror the maven-resources-plugin or maven-compiler-plugin, which simply emit an [INFO] level message and skip further execution if src/main/resources or src/main/java are missing.

(Note: A partial workaround exists, using <skip>true/false<true> and <inherited>false/true</inherited> trickery, but is not pretty – and only works for a single level of inheritance.)

@jochenw
Copy link
Member

jochenw commented Jul 18, 2020

Sounds reasonable to me. Will do.

@sewe
Copy link
Author

sewe commented Jul 24, 2020

Hi @jochenw. Excellent. Thanks for picking this up.

Out of curiosity: Do you already know what the default will be?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants