[
http://jira.codehaus.org/browse/MANTRUN-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161653#action_161653
]
Jochen Wiedmann commented on MANTRUN-91:
----------------------------------------
Carlos, I disagree with your diagnosis.
The antrun plugin should try to mimick the behaviour of Ant as much as
possible. Autodetecting the javac compiler is an important part of that
behaviour.
The requirement to specify dependencies via plugin configuration makes sense in
the case of custom tasks: With native Ant, one would have to specify -lib
options or do something similar, so its okay to require configuration. With
tools.jar, the case is different.
> Cannot run javac from tasks
> ---------------------------
>
> Key: MANTRUN-91
> URL: http://jira.codehaus.org/browse/MANTRUN-91
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
> Reporter: Thomas Diesler
> Assignee: Carlos Sanchez
>
> Embedded error: The following error occurred while executing this line:
> /home/tdiesler/svn/jbossws/stack/native/trunk/modules/testsuite/native-tests/scripts/antrun-wstools.xml:65:
> Unable to find a javac compiler;
> com.sun.tools.javac.Main is not on the classpath.
> Perhaps JAVA_HOME does not point to the JDK
--
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
