You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "fabrizio giustina (JIRA)" <ji...@codehaus.org> on 2005/11/26 14:42:08 UTC

[jira] Closed: (MNG-1604) Boot classpath incomplete in generated .classpath

     [ http://jira.codehaus.org/browse/MNG-1604?page=all ]
     
fabrizio giustina closed MNG-1604:
----------------------------------

     Assign To: fabrizio giustina
    Resolution: Fixed

Already fixed in svn, javadocs for plugin properties have been updated

> Boot classpath incomplete in generated .classpath
> -------------------------------------------------
>
>          Key: MNG-1604
>          URL: http://jira.codehaus.org/browse/MNG-1604
>      Project: Maven 2
>         Type: Bug
>   Components: maven-eclipse-plugin
>     Versions: 2.0
>  Environment: Eclipse 3.2M3
>     Reporter: Jochen Wiedmann
>     Assignee: fabrizio giustina

>
>
> The .classpath file, which is generated by the maven-eclipse-plugin, specifies the boot classpath as follows:
>     <classpathentry kind="var" rootpath="JRE_SRCROOT" path="JRE_LIB" sourcepath="JRE_SRC"/>
> Unfortunately, this entry doesn't include the complete boot classpath, but rt.jar only. But a modern JRE's (>= 1.4) boot classpath includes more jar files, for example jsse.jar, or jce.jar.
> Current workaround: Edit the generated .classpath file manually and replace the above line with
>     <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> Specifying this container in the classpathContainers property does *not* work: In that case, Eclipse refuses the generated .classpath file, because it contains both of the above two lines: The rt.jar file is specified twice.
> Suggested solutions:
>     a) Replace the JRE_LIB line with the container definition. I must admit, that I have no idea, whether this
>          works with previous Eclipse versions and which. Side effects seem possible.
>     b) Same thing than a), but optional: User must set a certain plugin property.
>     c) Check the classpathContainers property: If it does include the JRE_CONTAINER, then omit
>          the JRE_LIB line.
> I am ready to specify a patch for the plugin, if a developer decides which of the above solutions is the way to go or has another idea.

-- 
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