You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by mb...@apache.org on 2014/03/11 00:55:59 UTC
svn commit: r1576140 - in /commons/proper/weaver/trunk: pom.xml
src/site/markdown/building.md
Author: mbenson
Date: Mon Mar 10 23:55:58 2014
New Revision: 1576140
URL: http://svn.apache.org/r1576140
Log:
issue management; disallow Maven 3.2.x; document need for MaxPermGen on site build
Modified:
commons/proper/weaver/trunk/pom.xml
commons/proper/weaver/trunk/src/site/markdown/building.md
Modified: commons/proper/weaver/trunk/pom.xml
URL: http://svn.apache.org/viewvc/commons/proper/weaver/trunk/pom.xml?rev=1576140&r1=1576139&r2=1576140&view=diff
==============================================================================
--- commons/proper/weaver/trunk/pom.xml (original)
+++ commons/proper/weaver/trunk/pom.xml Mon Mar 10 23:55:58 2014
@@ -39,6 +39,11 @@ under the License.
<url>http://commons.apache.org/proper/commons-weaver</url>
+ <issueManagement>
+ <system>jira</system>
+ <url>http://issues.apache.org/jira/browse/WEAVER</url>
+ </issueManagement>
+
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
@@ -53,7 +58,6 @@ under the License.
<commons.site.path>commons-weaver</commons.site.path>
<asm.version>4.2</asm.version>
<commons.scmPubUrl>https://svn.apache.org/repos/infra/websites/production/commons/content/proper/${commons.site.path}</commons.scmPubUrl>
- <commons.project-info.version>2.6</commons.project-info.version>
<ant.version>1.9.3</ant.version>
<checkstyle.version>2.11</checkstyle.version>
@@ -261,6 +265,11 @@ under the License.
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-enforcer-plugin</artifactId>
+ <version>1.3.1</version>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>3.0.1</version>
</plugin>
@@ -399,7 +408,6 @@ under the License.
<inherited>true</inherited>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
- <version>1.3.1</version>
<executions>
<execution>
<id>enforce-maven-3</id>
@@ -409,7 +417,7 @@ under the License.
<configuration>
<rules>
<requireMavenVersion>
- <version>3.0.0</version>
+ <version>[3.0.0,3.2.0)</version>
</requireMavenVersion>
</rules>
<fail>true</fail>
Modified: commons/proper/weaver/trunk/src/site/markdown/building.md
URL: http://svn.apache.org/viewvc/commons/proper/weaver/trunk/src/site/markdown/building.md?rev=1576140&r1=1576139&r2=1576140&view=diff
==============================================================================
--- commons/proper/weaver/trunk/src/site/markdown/building.md (original)
+++ commons/proper/weaver/trunk/src/site/markdown/building.md Mon Mar 10 23:55:58 2014
@@ -29,7 +29,10 @@ various modules visible to one another u
Without installing to your local Maven repository, however, certain items
will always fail; e.g. `mvn clean` without `package`, `mvn dependency:list`,
`mvn dependency:tree`, and probably others. In general, `mvn install` will
-avoid further surprises down the line.
+avoid further surprises down the line. Additionally, there seems currently
+to be an issue with the recursive dependencies expressed in the Commons
+Weaver multimodule project structure when run with Maven 3.2.x; the project
+has been set to require Maven 3.0.0-3.1.x for the time being.
### Testing with security enabled
The Privilizer is the fundamental "guinea pig" weaver module.
@@ -40,13 +43,19 @@ always. The `example` and `ant/test` mod
You can run their tests with this profile enabled to turn on Java security.
### Antlib Test module
-Located at `ant/test`, this module\'s tests are implemented by unpacking the
+Located at `ant/test`, this module's tests are implemented by unpacking the
source of the `example` module and reusing it. For this reason, the
`example` module must have been packaged previously to executing the `ant/test`
tests, so in a multimodule build you should at least specify the `package`
-phase of the default lifecycle. Alternatively, you can disable this module\'s
+phase of the default lifecycle. Alternatively, you can disable this module's
tests by deactivating the profile in which they are set up: `antlib-test`.
Similarly, when building the project site you should deactivate the
-`antlib-test` profile, to stop this module\'s tests from requiring the
-`example` module to have been previously packaged.
+`antlib-test` profile, to stop these tests from requiring the `example` module
+to have been previously packaged.
+
+### Additional site building issues
+The Commons Weaver site runs out of permgen space when built with default JVM
+settings; the `MAVEN_OPTS` environment variable can be used to set `MaxPermGen`.
+`-XX:MaxPermGen=96m` seems to be adequate.
+