Author: brianf
Date: Mon Sep 8 13:19:13 2008
New Revision: 693237
URL: http://svn.apache.org/viewvc?rev=693237&view=rev
Log:
removed clirr config (see embedded comment) and enforcer version
Modified:
maven/pom/trunk/maven/pom.xml
Modified: maven/pom/trunk/maven/pom.xml
URL:
http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?rev=693237&r1=693236&r2=693237&view=diff
==============================================================================
--- maven/pom/trunk/maven/pom.xml (original)
+++ maven/pom/trunk/maven/pom.xml Mon Sep 8 13:19:13 2008
@@ -577,11 +577,12 @@
<artifactId>maven-deploy-plugin</artifactId>
<version>2.3</version>
</plugin>
- <plugin>
+ <!--<plugin>
+ Uncomment after alpha-4 is released...we have check or egg here doing
the release that introduces the rule that is needed.
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
- <version>1.0-SNAPSHOT</version>
- </plugin>
+ <version>1.0-alpha-4</version>
+ </plugin>-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-docck-plugin</artifactId>
@@ -758,7 +759,9 @@
</activation>
<build>
<plugins>
- <plugin>
+
+ <!--<plugin>
+ Clirr needs to be more flexble before we can force this everywhere.
New releases that don't have previous artifacts to compare cause Clirr to blow
up. And Clirr needs to be smart enough to only look at the previous release
artifact so we can make this work during snapshot builds, otherwise it just
blows up when you try to do a release.
<groupId>org.codehaus.mojo</groupId>
<artifactId>clirr-maven-plugin</artifactId>
<executions>
@@ -770,7 +773,7 @@
</goals>
</execution>
</executions>
- </plugin>
+ </plugin>-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
