rfscholte commented on pull request #357:
URL: https://github.com/apache/maven/pull/357#issuecomment-638413122
It looks like you're still trying to convince me that wildcards are
necessary. Your issue was the license check on the verify phase, I gave you one
solution how to move them to
rfscholte commented on pull request #357:
URL: https://github.com/apache/maven/pull/357#issuecomment-637789710
```
license
com.mycila
license-maven-plugin
rfscholte commented on pull request #357:
URL: https://github.com/apache/maven/pull/357#issuecomment-637770365
I don't know the plugin, but I would start there. Ask if they can improve it
to handle different licenses.
Next I would look into profiles, i.e. `mvn validate -Plicenses`, and
rfscholte commented on pull request #357:
URL: https://github.com/apache/maven/pull/357#issuecomment-637123202
Maven is lifecycle driven. Being able to execute a goal from commandline is
a feature, but I don't see the need to execute all available exeucutionIds.
Most likely this will have
