[ http://jira.codehaus.org/browse/MNG-1334?page=comments#action_53264 ]
Kenney Westerhof commented on MNG-1334:
---------------------------------------
The preferred way is this:
<build>
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<dependencies>
<dependency>
<groupId>sun</groupId>
<artifactId>tools</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
</dependencies>
<executions>
<execution>
<phase>generate-test-sources</phase>
<configuration>
<tasks>
<rmic verify="true" debug="on"
base="${project.build.outputDirectory}">
....
</rmic>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
> classpath related error when invoking the rmic task from maven
> --------------------------------------------------------------
>
> Key: MNG-1334
> URL: http://jira.codehaus.org/browse/MNG-1334
> Project: Maven 2
> Type: Bug
> Components: maven-antrun-plugin
> Versions: 2.0
> Environment: OpenSuSE 10, JDK1.5, Maven 2.0
> Reporter: Rohnny Moland (JIRA)
> Assignee: Brett Porter
>
>
> When invoking the rmic task from maven, I get this error message:
> "Cannot use SUN rmic, as it is not available. A common solution is to
> set the environment variable JAVA_HOME or CLASSPATH."
> Invoking the rmic task from ant works fine. So it must be a classpath problem
> when using ant embedded in maven.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]