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

Can this be extended to include the plugin version and configuration? #11

Open
bradleysmithllc opened this issue May 23, 2018 · 3 comments

Comments

@bradleysmithllc
Copy link

Perhaps as a verbose option? I recently wrestled with a build and the problem ended up being that I had removed the version tag and maven apparently chooses the worst version in that case.

I was trying to verify that configuration was propagating properly from pluginManagement to build/plugins. So, I wanted to verify the configuration but also the version number would have immediately clued me in.

Considering how difficult maven poms can be to work with I really don't understand why this type of plan is not built in.

@jcgay
Copy link
Member

jcgay commented May 25, 2018

Have you tried mvn help:effective-pom (https://maven.apache.org/plugins/maven-help-plugin/effective-pom-mojo.html) ?

I'll have a look if It can be interesting to add such features, the version should not really be a big deal but the configuration information would need a new goal (and may be out of the buildplan scope).

@bradleysmithllc
Copy link
Author

bradleysmithllc commented Jun 4, 2018 via email

@hboutemy
Copy link
Member

hboutemy commented Jun 5, 2022

configuration is definitively the purpose of help:effective-pom

@jcgay plugins version would be nice

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

3 participants