The Maven team is pleased to announce the release of the Maven Enforcer Plugin, version 1.0-alpha-4
The Enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more standard rules and user created rules. http://maven.apache.org/plugins/maven-enforcer-plugin/ You should specify the version in your project's plugin configuration: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <version>1.0-alpha-4</version> </plugin> Release Notes - Maven 2.x Enforcer Plugin - Version 1.0-alpha-4 ** Bug * [MENFORCER-10] - EnforcerRuleHelper#getComponent() throws exception * [MENFORCER-12] - enforce-once still runs in each child pom * [MENFORCER-27] - Multi model project with enforcer plugin bug * [MENFORCER-37] - 'noSnapshots' rule do not check version of parent * [MENFORCER-45] - does not detect version for plugin configured in profiles ** Improvement * [MENFORCER-11] - enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it. * [MENFORCER-18] - Bean shell enforcer swallows message * [MENFORCER-21] - allow includes to fine tune excludes in bannedDependencies * [MENFORCER-38] - Enforcer rules for AlwaysPass and AlwaysFail * [MENFORCER-43] - RequireReleaseDeps - allow to execute "onlyWhenRelease" * [MENFORCER-44] - the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" and timestamps ** New Feature * [MENFORCER-15] - add a rule to enforce that all plugins have a declared version * [MENFORCER-22] - create a rule to check the current project is not a snapshot ** Task * [MENFORCER-32] - Add svn:eol-style=native to source files * [MENFORCER-33] - Tidy up EvaluateBeanshell rule * [MENFORCER-34] - Make code Java 1.4 compatible Enjoy, -The Maven team --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
