You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Oddmar Sandvik (JIRA)" <ji...@codehaus.org> on 2005/09/21 09:39:10 UTC
[jira] Created: (MNG-937) Incorrect JRE classpath entry in eclipse .classpath file
Incorrect JRE classpath entry in eclipse .classpath file
--------------------------------------------------------
Key: MNG-937
URL: http://jira.codehaus.org/browse/MNG-937
Project: Maven 2
Type: Bug
Components: maven-eclipse-plugin
Versions: 2.0-beta-1
Environment: WinXP, JDK 1.5
Reporter: Oddmar Sandvik
This is an issue that was pointed out on this mailinglist in 2003 on maven 1.0 and eclipse:
When I run "maven eclipse", it generates the .classpath file with the
following entry:
<classpathentry kind="var" rootpath="JRE_SRCROOT" path="JRE_LIB"
sourcepath="JRE_SRC"/>
whereas when I create a project in Eclipse, a reference to JRE_LIB is
written as:
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
With the former setting, your classpath only includes rt.jar, and
nothing else. As a result, you may fail to import some classes like
javax.net.*, which sits in a different jar file.
This seems to be sorted out in maven 1. However, "m2 eclipse:eclipse" has the same problem today. I must edit the .classpath file manually after generation - but this is of course overwritten whenever dependencies change and is not a tenable option.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-937) Incorrect JRE classpath entry in eclipse .classpath file
Posted by "Johnny R. Ruiz III (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-937?page=all ]
Johnny R. Ruiz III updated MNG-937:
-----------------------------------
Attachment: MNG-937-maven-eclipse-plugin.patch
I updated EclipseClasspathWriter and as well as Test Projects.
This patches the requested improvement.
Please apply. Thanks a lot!
> Incorrect JRE classpath entry in eclipse .classpath file
> --------------------------------------------------------
>
> Key: MNG-937
> URL: http://jira.codehaus.org/browse/MNG-937
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Versions: 2.0 (RC)
> Environment: WinXP, JDK 1.5
> Reporter: Oddmar Sandvik
> Assignee: Johnny R. Ruiz III
> Attachments: MNG-937-maven-eclipse-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> This is an issue that was pointed out on this mailinglist in 2003 on maven 1.0 and eclipse:
> When I run "maven eclipse", it generates the .classpath file with the
> following entry:
>
> <classpathentry kind="var" rootpath="JRE_SRCROOT" path="JRE_LIB"
> sourcepath="JRE_SRC"/>
>
> whereas when I create a project in Eclipse, a reference to JRE_LIB is
> written as:
>
> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>
> With the former setting, your classpath only includes rt.jar, and
> nothing else. As a result, you may fail to import some classes like
> javax.net.*, which sits in a different jar file.
> This seems to be sorted out in maven 1. However, "m2 eclipse:eclipse" has the same problem today. I must edit the .classpath file manually after generation - but this is of course overwritten whenever dependencies change and is not a tenable option.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-937) Incorrect JRE classpath entry in eclipse .classpath file
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-937?page=all ]
Brett Porter closed MNG-937:
----------------------------
Resolution: Fixed
Fix Version: 2.0.1
applied
> Incorrect JRE classpath entry in eclipse .classpath file
> --------------------------------------------------------
>
> Key: MNG-937
> URL: http://jira.codehaus.org/browse/MNG-937
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Versions: 2.0 (RC)
> Environment: WinXP, JDK 1.5
> Reporter: Oddmar Sandvik
> Assignee: Johnny R. Ruiz III
> Fix For: 2.0.1
> Attachments: MNG-937-maven-eclipse-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> This is an issue that was pointed out on this mailinglist in 2003 on maven 1.0 and eclipse:
> When I run "maven eclipse", it generates the .classpath file with the
> following entry:
>
> <classpathentry kind="var" rootpath="JRE_SRCROOT" path="JRE_LIB"
> sourcepath="JRE_SRC"/>
>
> whereas when I create a project in Eclipse, a reference to JRE_LIB is
> written as:
>
> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>
> With the former setting, your classpath only includes rt.jar, and
> nothing else. As a result, you may fail to import some classes like
> javax.net.*, which sits in a different jar file.
> This seems to be sorted out in maven 1. However, "m2 eclipse:eclipse" has the same problem today. I must edit the .classpath file manually after generation - but this is of course overwritten whenever dependencies change and is not a tenable option.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-937) Incorrect JRE classpath entry in eclipse .classpath file
Posted by "Johnny R. Ruiz III (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-937?page=all ]
Johnny R. Ruiz III updated MNG-937:
-----------------------------------
Assign To: Johnny R. Ruiz III
Version: (was: 2.0-beta-1)
2.0 (RC)
Remaining Estimate: 3 hours
Original Estimate: 10800
> Incorrect JRE classpath entry in eclipse .classpath file
> --------------------------------------------------------
>
> Key: MNG-937
> URL: http://jira.codehaus.org/browse/MNG-937
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Versions: 2.0 (RC)
> Environment: WinXP, JDK 1.5
> Reporter: Oddmar Sandvik
> Assignee: Johnny R. Ruiz III
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> This is an issue that was pointed out on this mailinglist in 2003 on maven 1.0 and eclipse:
> When I run "maven eclipse", it generates the .classpath file with the
> following entry:
>
> <classpathentry kind="var" rootpath="JRE_SRCROOT" path="JRE_LIB"
> sourcepath="JRE_SRC"/>
>
> whereas when I create a project in Eclipse, a reference to JRE_LIB is
> written as:
>
> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>
> With the former setting, your classpath only includes rt.jar, and
> nothing else. As a result, you may fail to import some classes like
> javax.net.*, which sits in a different jar file.
> This seems to be sorted out in maven 1. However, "m2 eclipse:eclipse" has the same problem today. I must edit the .classpath file manually after generation - but this is of course overwritten whenever dependencies change and is not a tenable option.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org