[
http://jira.codehaus.org/browse/MECLIPSE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94150
]
Jasper Rosenberg commented on MECLIPSE-253:
-------------------------------------------
We are seeing the same issue, and it is a hassle as some developers are on XP
and some are on OS X.
> eclipse:eclipse should use classpath variable JAVA_HOME or JDK_HOME when
> writing .classpath for tools.jar
> ---------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-253
> URL: http://jira.codehaus.org/browse/MECLIPSE-253
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Environment: All.
> Reporter: Parag Mehta
>
> Classpath generated by eclipse:eclipse contains absolute reference to the jdk
> being used
> <classpathentry kind="lib" path="C:/app/Java/jdk1.5.0_11/lib/tools.jar"/>
> This creates a classpath that is not portable amongst multiple
> machines/developers (who may have the jdk installed elsewhere). Using
> variables like JAVA_HOME or JDK_HOME would yield a more portable result (like
> users are expected to define M2_REPO or the plugin can do so).
> <classpathentry kind="lib" path="JAVA_HOME/lib/tools.jar"/>
> Thanks.
--
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
