[
http://jira.codehaus.org/browse/MANTRUN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135753#action_135753
]
Tim Fliss commented on MANTRUN-20:
----------------------------------
I agree. Normal doesn't mean correct. referencing tools.jar seems to be the
workaround (an unsatisfactory one if you need to build on macs because of all
the extra profile settings). If java.home pointed at the actual java.home set
by the user, and would find tools.jar on its own. In any case a better
explanation would help.
> Antrun plugin defaults to using jre classpath instead of jdk
> ------------------------------------------------------------
>
> Key: MANTRUN-20
> URL: http://jira.codehaus.org/browse/MANTRUN-20
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
> Reporter: ruel loehr
> Assignee: Brett Porter
>
> When executing ant tasks via the antrun plugin, maven reconciles them with a
> jre classpath. You can verify this by running the antrun plugin with the
> following task:
> <echo message="{java.home"/>
> The solution I can see is to add a plugin dependency on the antrun plugin
> which resolves to the tools.jar, however another bug prevents this from
> working in anything but top level projects. Hence, the antrun plugin cannot
> be used for any compilation purposes (javac, rmic) for child projects.
--
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
