The smartics-enforcer-rules have been released with version 0.2.0.
This version provides a new rule called NoSnapshotsInDependencyManagementRule, which - you might already have guessed - checks that there are no snapshot dependencies in the dependency management block of a Maven POM.
If you are building with Maven, it is easy to make a release of project with snapshot dependencies. Not in the dependencies block, the maven-release-plugin takes care of that, but in the dependency management block (and unfortunately in some other places, like the skin artifact for building the Maven site).
This rule for the maven-enforcer-plugin checks that no dependencies listed in the management block are snapshots. So, especially for BOMs, you will never again have a release that fails to have set the dependency management information to proper releases.
This version provides a new rule called NoSnapshotsInDependencyManagementRule, which - you might already have guessed - checks that there are no snapshot dependencies in the dependency management block of a Maven POM.
The Problem
If you are building with Maven, it is easy to make a release of project with snapshot dependencies. Not in the dependencies block, the maven-release-plugin takes care of that, but in the dependency management block (and unfortunately in some other places, like the skin artifact for building the Maven site).
The solution
This rule for the maven-enforcer-plugin checks that no dependencies listed in the management block are snapshots. So, especially for BOMs, you will never again have a release that fails to have set the dependency management information to proper releases.
