-
Notifications
You must be signed in to change notification settings - Fork 126
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
Update build plugins #129
Update build plugins #129
Conversation
<plugin> | ||
<groupId>org.apache.maven.plugins</groupId> | ||
<artifactId>maven-jxr-plugin</artifactId> | ||
<version>3.1.1</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is used twice, make it a property
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This above is in pluginMgmt, and removed the version from one in profile, as it will use the value from pluginMgmt.
@michael-o ping |
Enforcer as is causes that downstream in case of update POM must completely redefine plugin, thus, loosing all the benefits of parent POM pluginMgmt. Move plugin definition to pluginMgmt instead to fully define it and it's dependines in plugin section. Keep execution in plugin section. Update to latest enforcer as well. ------ See for example apache/maven-resolver#129
Make it clear that "it only works with Sisu" is meant for integrators, not "end users" wishing to use them with Maven.
I am really unsure why we do this and do we do this right at all. So am not toching this plugin for now.
Update plugins. Enforcer is tricky, as it was in pluginMgmt, but in parent is in plugins, and extra rules are not picked up otherwise.