Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/khmarbaise/uptodate-maven-plugin
uptodate-maven-plugin
https://github.com/khmarbaise/uptodate-maven-plugin
java maven maven-plugin
Last synced: 3 months ago
JSON representation
uptodate-maven-plugin
- Host: GitHub
- URL: https://github.com/khmarbaise/uptodate-maven-plugin
- Owner: khmarbaise
- Created: 2014-03-21T19:34:33.000Z (almost 11 years ago)
- Default Branch: master
- Last Pushed: 2018-09-05T17:31:13.000Z (over 6 years ago)
- Last Synced: 2024-09-29T16:41:08.019Z (4 months ago)
- Topics: java, maven, maven-plugin
- Language: Java
- Homepage: https://khmarbaise.github.io/uptodate-maven-plugin/
- Size: 507 KB
- Stars: 5
- Watchers: 4
- Forks: 4
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
UpToDate-Maven-Plugin
=====================License
-------
[Apache License, Version 2.0, January 2004](http://www.apache.org/licenses/)Overview
--------Force the use of the most up-to-date released versions of an artifact.
[The Basic idea for this plugin was born based on the discussion about the enforcer rule](https://issues.apache.org/jira/browse/MENFORCER-190).
Sometimes you have a situation like using a parent pom but you would like to
force the users in your company to use the newest version cause there had been changes
which need for further development. This plugin can help in such situations.Parent Check
------------The following pom snippet will show an example of a usual project which
is using a parent:
com.soebes.maven.plugins.test.integration
parent
0.2
org.test.parent
root
1.0.0-SNAPSHOTSo basically no problem at all. But what happens if a new version
of that parent is released and you want to force people to use that
new version? Simply you add the following definition to your project:So every time you try to build this plugin will check if
the parent is the newest version.
com.soebes.maven.plugins
uptodate-maven-plugin
force-updrage
parent
validate
If it is not the newest version it will break the build.
Furtunate you can skip that breaking by using the following
property on command if you really need.mvn -Duptodate.skip=true ...
Dependency Check
----------------Default
checking all dependencies of the current module if they are up-to-date.Lets assume you have the following dependency in your pom:
org.xyz.test
the-artifact
1.3
Sometime you must be sure to use always the newest version which is available.
Using the uptodate-maven-plugin will exactly check this situation.
If you need to check the parent of a parent to be always uptodate you
could use the parent goal:
com.soebes.maven.plugins
uptodate-maven-plugin
check-dependencies
dependency
validate
..