I've replicated this problem in some of my own projects. It seems that
the key is to have the compiler plugin configured in the
pluginManagement section of the POM, and then to enable a report like
the javadoc reports that will cause the lifecycle to fork and compile
sources. At that point, it seems to lose the pluginManagement section,
but I haven't gotten into it far enough to know why yet.
The JIRA issue is: http://jira.codehaus.org/browse/MNG-3743
Christian Schulte wrote:
Martin Höller wrote:
Hi!
On Thursday 04 September 2008 John Casey wrote:
On the last go around, we had one issue pop up with maven plugin builds
(though it might also apply to build extensions in the reactor as well).
I've fixed it, and now here's the lucky 13th release candidate:
http://people.apache.org/~jdcasey/stage/apache-maven/2.1.0-M1-RC13/org/ap
ache/maven/apache-maven/2.1.0-M1-RC13/
Please give it a spin (especially you, Arnaud! :) ), and let me know if
you have any trouble.
Building (compiling, testing, packaging, installing) our multimodule
projects works without problems in 2.0.9 and 2.1.*.
However, I found one problem with site generation: when executing
'mvn site' I get the following error:
[INFO] [compiler:compile]
[INFO] Compiling 6 source files to
/home/martin/svndir/emcs/emcs-common/target/classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
/home/martin/svndir/emcs/emcs-common/src/main/java/at/co/xss/emcs/util/Pair.java:[33,17]
generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public class Pair<A, B>
I configured the maven compiler plugin in the parent's <pluginManagement>
section as follows:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.0.2</version>
<configuration>
<source>1.5</source>
<target>1.5</target>
<encoding>${fileEncoding}</encoding>
</configuration>
</plugin>
Compilation works fine when executing 'mvn compile'. Mith maven 2.0.9
'mvn site' also works with no problems but not with 2.1.0-M1-RC13.
I'm using maven-site-plugin version 2.0-beta-7.
Any ideas?
- martin
Hi,
similar problem here. mvn install works, mvn site gives compile error.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
...src/test/java/SerializableUtility.java:[53,19] ';' expected
...src/test/java/SerializableUtility.java:[53,19] ';' expected
That line reads:
assert args.length == 1;
As it seems, the site plugin cannot compile assertions with
2.1.0-M1-RC13 anymore. Generating the site with maven 2.0.9 works.
mvn help:effective-pom shows
<plugin>
<artifactId>maven-site-plugin</artifactId>
<version>RELEASE</version>
<configuration>
<outputEncoding>UTF-8</outputEncoding>
<inputEncoding>UTF-8</inputEncoding>
<locales>en</locales>
</configuration>
</plugin>
for both, 2.0.9 and 2.1.0-M1-RC13.
I can work around the compile error by first compiling by using e.g. mvn
install before doing a mvn site since that way, the site plugin does not
need to compile anything. Doing mvn clean followed by mvn site leads to
the compile error, however.
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
