For anyone that may be interested... I found a solution that forces
source code to be compiled using a custom eclipse JDT compiler version
(non-plexus):
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.0.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
<compilerVersion>1.6</compilerVersion>
<fork>true</fork>
<executable>java -classpath
${env.M2_REPO}/org/eclipse/jdt/${org.eclipse.jdt.core.version}/core-${or
g.eclipse.jdt.core.version}.jar
org.eclipse.jdt.internal.compiler.batch.Main -classpath rt.jar
-sourcepath "src/main"</executable>
</configuration>
<dependencies>
<dependency>
<groupId>org.eclipse.jdt</groupId>
<artifactId>core</artifactId>
<version>${nem.eclipse.jdt.version}</version>
</dependency>
</dependencies>
</plugin>
...
<!-- Need to add repository that has the latest JDT version (at the time
of this post repo1 only had 3.3.x) -->
<repositories>
<repository>
<id>jboss</id>
<url>http://repository.jboss.com/maven2/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
...
<properties>
<org.eclipse.jdt.core.version>3.4.2.v_883_R34x</org.eclipse.jdt.version>
</properties>
...
-----Original Message-----
From: Hoover, William [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2008 2:49 PM
To: users@maven.apache.org
Subject: maven-compiler-plugin using eclipse
In maven version 2.0.8 we originally tried the following, but it did not
resolve the generics issue that the plexus compiler has related to
http://jira.codehaus.org/browse/PLXCOMP-100:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<dependencies>
<dependency>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-compiler-eclipse</artifactId>
<version>1.5</version>
</dependency>
</dependencies>
</plugin>
... so we had to use the following settings to get maven to use the same
eclipse compiler that we were using in our ide environment (provided we
dropped the jar in maven/lib):
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<fork>true</fork>
<compilerVersion>1.6</compilerVersion>
<executable>java -classpath
${MAVEN_HOME}/lib/org.eclipse.jdt.core_X.jar
org.eclipse.jdt.internal.compiler.batch.Main -classpath rt.jar
-sourcepath "src/main"</executable>
</configuration>
</plugin>
In maven 2.0.9 using the above hack results in an exception. We even
tried a suggestion that was found on a forum:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<dependencies>
<dependency>
<groupId>org.eclipse.jdt</groupId>
<artifactId>core</artifactId>
<version>3.3.0-v_771</version>
</dependency>
</dependencies>
</plugin>
The above had issues of it's own due to the common dependency version
range (we resolved by manually installing in our company repository). It
still did not work. Does anyone know how to accomplish this?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
