![]() Unless otherwise stated, all core annotations are located in the package Relative Execution Order of User Code and Extensions Providing Invocation Contexts for Test Templates Before and After Test Execution Callbacks Running JUnit 4 Tests on the JUnit Platform Dependency Injection for Constructors and Methods Changing the Default Test Instance Lifecycle ![]() Operating System and Architecture Conditions ![]() Setting the Default Display Name Generator Meta-Annotations and Composed Annotations Only get INFO lines and the module header Here is a script that will turn the above logs into a html page you can directly view ( Download): #!/usr/bin/groovyĭef lines = System.in.newReader().readLines() And unfortunately the Versions plugin does not have that feature so I had to improvize. What I instead would like to do is generate a HTML report for every build that only displays the dependencies in table form. That is great as it displays all the information we need!īut it is not nice to have to go through the build logs every time to see if a dependency has changed in that output. Require Maven 3.0 to use the following plugin updates: Require Maven 2.2.1 to use the following plugin updates: Require Maven 2.2.0 to use the following plugin updates: Require Maven 2.1.0 to use the following plugin updates: Require Maven 2.0.9 to use the following plugin updates: Require Maven 2.0.6 to use the following plugin updates: Require Maven 2.0.2 to use the following plugin updates: Require Maven 2.0.1 to use the following plugin updates: force the maven version which is needed to build this project. Update the pom.xml to contain maven-enforcer-plugin to Project does not define required minimum version of Maven. versions and may be influencing the plugins required minimum Maven Note: the super-pom from Maven 3.3.9 defines some of the plugin Plugins require minimum Maven version of: 3.0 Project does not define minimum Maven version, default is: 2.0 The following plugins do not have their version specified: All plugins with a version specified are using the latest versions. versions-maven-plugin:2.5:display-plugin-updates (default-cli) dependency-report. The following dependencies in Dependencies have newer versions: versions-maven-plugin:2.5:display-dependency-updates (default-cli) dependency-report. Building dependency-report Maven Webapp 1.0-SNAPSHOT If I run mvn versions:display-dependency-updates versions:display-plugin-updates on a small example project you might get the following output: $ mvn versions:display-dependency-updates versions:display-plugin-updates But one particular feature is really interesting here, and that is the display-plugin-updates feature of the Versions plugin. With the versions plugin you can pretty easily get reports of what dependencies you have and what versions they have. So the thing I wanted to create was something I could run on a CI and that could generate a report I could put on a dashboard where I could see what dependencies were getting old and what I needed to update. I recently was in the situation that I inherited an old project and the first thing I wanted to do was to get the project updated to more recent dependencies to fix security vulnerabilities and to start supporting new technologies that require more modern versions of the libraries.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |