|
Hi, when I run mvn versions:display-plugin-updates, the goal does not bother outputting plugins with the latest version, instead it thankfully just says: "All plugins with a version specified are using the latest versions." This helps me when I'm scrolling through the output of multiple submodules POMs, as I only see the out-of-date/undeclared plugins instead of being distracted by lists of up-to-date plugins:
[INFO] ------------------------------------------------------------------------
[INFO] Building – Service WAR file 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] — versions-maven-plugin:3.0-SNAPSHOT:display-plugin-updates (default-cli) @ cxf-soap-over-jms-war —
[INFO]
[INFO] All plugins with a version specified are using the latest versions.
[INFO]
[WARNING] The following plugins do not have their version specified:
[WARNING] maven-clean-plugin .......................... (from super-pom) 2.5
...several more...
[INFO]
[INFO] Project inherits minimum Maven version as: 3.0
[INFO] Plugins require minimum Maven version of: 2.2.1
[INFO] Note: the super-pom from Maven 3.0.4 defines some of the plugin
[INFO] versions and may be influencing the plugins required minimum Maven
[INFO] version.
[INFO]
[INFO] No plugins require a newer version of Maven than specified by the pom.
[INFO]
However, mvn versions:display-dependency-updates unfortunately does list up-to-date dependencies, a distraction when I need to quickly go through to scan which dependencies are out-of-date:
[INFO] — versions-maven-plugin:3.0-SNAPSHOT:display-dependency-updates (default-cli) @ cxf-soap-over-jms-service —
[INFO] The following dependencies in Dependency Management are using the newest version:
[INFO] junit:junit ..................................................... 4.11
[INFO] org.apache.cxf:cxf-rt-frontend-jaxws ........................... 2.7.1
[INFO] org.apache.cxf:cxf-rt-transports-http .......................... 2.7.1
[INFO] org.apache.cxf:cxf-rt-transports-http-jetty .................... 2.7.1
[INFO] org.apache.cxf:cxf-rt-ws-mex ................................... 2.7.1
[INFO] org.apache.cxf:cxf-rt-ws-security .............................. 2.7.1
[INFO] org.apache.cxf.services.sts:cxf-services-sts-core .............. 2.7.1
[INFO] org.apache.derby:derby ...................................... 10.9.1.0
[INFO]
[INFO] The following dependencies in Dependency Management have newer versions:
[INFO] javax.servlet:servlet-api ......................... 2.5 -> 3.0-alpha-1
[INFO] org.glassfish.metro:webservices-rt ............... 2.2.1-1 -> 2.3-b100
[INFO] org.slf4j:slf4j-jdk14 ................................. 1.6.2 -> 1.7.2
[INFO] org.slf4j:slf4j-simple ................................ 1.6.2 -> 1.7.2
[INFO] org.springframework:spring-beans ...... 3.0.7.RELEASE -> 3.1.3.RELEASE
[INFO] org.springframework:spring-context .... 3.0.7.RELEASE -> 3.2.0.RELEASE
[INFO] org.springframework:spring-web ........ 3.0.7.RELEASE -> 3.2.0.RELEASE
[INFO]
[INFO] The following dependencies in Dependencies are using the newest version:
[INFO] org.apache.activemq:activemq-core .............................. 5.7.0
[INFO] org.apache.cxf:cxf-rt-transports-jms ........................... 2.7.1
[INFO]
[INFO] No dependencies in Dependencies have newer versions.
The attached patch has display-dependency-updates work similar to display-plugin-updates in that it will no longer list dependencies in either Dependencies or Dependency Management that are already using the latest version. That way the user by default will just see lists of dependencies that need potential updating without scanning over noise. To maintain the present capability for those who want it, I'm adding a "verbose" flag (defaulted to false) that will continue to output the already up-to-date dependencies.
|
