A Java 11+ command line tool to check for artifact updates of Maven and Gradle projects.
MvnCheck aims to help developers to keep their projects up-to-date by checking for last available dependency and plugin versions. Unlike some existing Maven plugins, MvnCheck uses an advanced filtering system to choose the most relevant update version for an artifact.
- Standalone and portable
- Recursive build files lookup
- Compact and comprehensible output
- Smart filtering to exclude non-release versions
- Smart filtering to select versions with the same qualifier (if any)
- Possibility to filter specific artifacts or update versions using ignore files
- Use any already installed Maven configuration and repository
- Use any already installed Gradle installation if available, or download a wrapper distribution
2 build file(s) found, checking for artifact updates
my-gradle-project\build.gradle
[COMPILE ONLY] com.google.guava:guava 31.0-android -> 33.0.0-android
1 artifact update(s) available
my-maven-project\pom.xml
[DEPENDENCY] org.apache.commons:commons-lang3 3.10 -> 3.14.0
[BUILD PLUGIN] org.apache.maven.plugins:maven-compiler-plugin 3.10.0 -> 3.12.1
2 artifact update(s) available
2/2 build file(s) checked, 3 artifact update(s) available
MvnCheck is running on most operating systems, it only requires Java 11 or higher to be installed.
You can check that Java is available in your environment and its version using the following command:
java -versionYou can download binaries for the latest version of MvnCheck on the release page.
Execute following commands in the folder where the downloaded archive file is located:
sudo tar -xvzf mvn-check-1.5.0-bin.tar.gz --directory /opt
export PATH=$PATH:/opt/mvn-check-1.5.0/binExtract the content of the downloaded archive file and move the extracted folder to C:\mvn-check-1.5.0, then:
- Right-click on the Windows icon and select "System"
- On the right, click on "Advanced system settings"
- In the new window, click on "Environment Variables..."
- Find the "Path" variable, choose "Edit", and add
;C:\mvn-check-1.5.0\binat the end
If MvnCheck is correctly installed, this command should work as expected:
mvnchk --versionusage: mvnchk [<path>] [-d <arg>] [-h] [-i] [--ignore-inherited] [-s] [-v]
-d,--max-depth <arg> Maximum depth of subdirectories to find build
files (a non-negative integer)
-h,--help Display help information
-i,--ignore-snapshots Ignore build file artifacts with a snapshot
version
--ignore-inherited Ignore build file artifacts with an inherited
version
-s,--short Only show build files with at least one artifact
update
-v,--version Display version information
MvnCheck allows to ignore artifacts or update versions by having a .mvnchk-ignore file:
- globally in the user home
- specifically in a project directory.
Here is an example of how to write it:
# Ignore a specific artifact
com.google.guava:guava
# Ignore a specific artifact update version
com.google.guava:guava:30.0-android
# Ignore artifact update versions using the "any characters" wildcard
com.google.guava:guava:*-android
# Ignore artifact update versions using the "any single character" wildcard
com.google.guava:guava:30.?-android
The table below shows which version of Maven and Gradle is used by each MvnCheck release. However, a higher version of a build tool may still be compatible.
| MvnCheck version | Maven version | Gradle version |
|---|---|---|
| 1.5.0 | 3.9.6 | 8.6 |
| 1.4.2 | 3.9.5 | 8.5 |
| 1.4.1 | 3.9.5 | 8.4 |
| 1.4.0 | 3.9.4 | 8.3 |
| 1.3.2 | 3.9.3 | 8.2.1 |
| 1.3.1 | 3.9.3 | 8.1.1 |
| 1.3.0 | 3.9.2 | 8.1.1 |
| 1.2.1 | 3.9.1 | 8.1.1 |
| 1.2.0 | 3.9.1 | 8.1 |
| 1.1.3 | 3.9.1 | 8.0.2 |
| 1.1.2 | 3.9.0 | 8.0.2 |
| 1.1.1 | 3.9.0 | 8.0.1 |
| 1.1.0 | 3.9.0 | 7.6 |
| 1.0.1 | 3.8.7 | 7.6 |
| 1.0.0 | 3.8.6 | 7.6 |
Note: Gradle is compatible starting with Gradle 4.8.
This project is licensed under the MIT License.