You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
That’s helpful, but sometimes (like what I was just doing) it was difficult to figure out exactly which versions were being used with which plugins etc. I will look at effective pom again, but I am pretty sure it didn’t do what I wanted.
Bradley Smith,
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.
The text was updated successfully, but these errors were encountered: