With all these updates to plugins it would be convenient if the versions
plugin worked as before. I still have to downgrade each time before checking
mvn -N wrapper:wrapper -Dmaven=3.5.4
./mvnw -N versions:display-plugin-updates -DgenerateBackupPoms=false
The project has a fair number of open issues and pull requests and hasn't
been updated for over a year now.
I don't have insight into the code, but perhaps the difficulties keeping it
up-to-date would be mitigated with tighter integration into Maven.
Managing dependencies is my main requirement of Maven, but a lot of this
work is left to the maven-dependency-plugin and the (Outside The Maven
Land) versions-maven-plugin.
Looking at the goals in these 2 plugins it seems most are invoked ad-hoc
anyway.
I have written dependency:copy into my build, but its a fringe case
(neither install/deploy plugins place artefacts as freely).
Its reasonable in the beginning of a project to implement a pluggable
architecture, but once the feature rush is over its often a good idea to
simplify that complexity into the core.
Could their logic be folded into version 4/5 of
https://maven.apache.org/ref/3.8.4/ somehow?
At the very least the plugins seem to overlap and could probably be merged.
Just throwing around ideas.
Thanks,
Delany
