Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7A325C3D1 for ; Sun, 30 Jun 2013 19:56:00 +0000 (UTC) Received: (qmail 23095 invoked by uid 500); 30 Jun 2013 19:55:58 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 22658 invoked by uid 500); 30 Jun 2013 19:55:57 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 22201 invoked by uid 99); 30 Jun 2013 19:55:57 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Jun 2013 19:55:57 +0000 Received: from localhost (HELO columbia) (127.0.0.1) (smtp-auth username rfscholte, mechanism login) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Jun 2013 19:55:57 +0000 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes Date: Sun, 30 Jun 2013 21:55:53 +0200 Subject: [ANN] Apache Maven Enforcer Plugin 1.3 Released To: announce@maven.apache.org, users@maven.apache.org Cc: dev@maven.apache.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Robert Scholte" Message-ID: User-Agent: Opera Mail/12.15 (Win32) The Apache Maven team is pleased to announce the release of the Maven Enforcer Plugin, version 1.3 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/enforcer/maven-enforcer-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-enforcer-plugin 1.3 Release Notes - Apache Maven 2.x Enforcer Plugin - Version 1.3 ** Bug * [MENFORCER-42] - Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository * [MENFORCER-123] - BannedDependencies version number not taken into account * [MENFORCER-126] - requirePluginVersions misreports plugins with artifactIds defined through properties * [MENFORCER-146] - requireUpperBoundDeps inneffective when DependencyManagement is used * [MENFORCER-148] - Broken hyperlink on Enforcer plugin usage page * [MENFORCER-149] - Broken links to properties of "Require OS Version" of Maven Enforcer Plugin * [MENFORCER-155] - Add rule RequirePrerequisite ** Improvement * [MENFORCER-83] - Banned dependencies should support regular expressions * [MENFORCER-134] - Require Upper Bound Dependencies and matching Snapshot Dependencies ** New Feature * [MENFORCER-74] - The bannedDependencies rule should support classifier * [MENFORCER-75] - The bannedDependencies rule should support scope condition * [MENFORCER-147] - Add RequireSameVersions * [MENFORCER-152] - Add Rule: BanDuplicatePomDependencyVersion or RequireUniquePomDependencyVersion ** Task * [MENFORCER-153] - Use Mock Repository Manager for ITs * [MENFORCER-154] - Update maven-dependency-tree to 2.1 to make it work with Maven-3.1+ Enjoy, -The Apache Maven team --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org