Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.6
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Eclipse 2.1.2, Maven 1.0 RC2, Maven Eclipse Plugin 1.6
    • Number of attachments :
      1

      Description

      When I create a project inside eclipse, the built-in JRE classpath inclues: rt.jar, sunrsasign.jar, jsse.jar, jce.jar, charsets.jar, dnsns.jar, sunjce_provider.jar, ldapsec.jar, localedata.jar

      This all comes from the following .classpath entry AFAIK:
      <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>

      The only entry I get when I use maven-eclipse to generate the the .classpath, the only entry I get is rt.jar from:

      <classpathentry kind="var" rootpath="JRE_SRCROOT" path="JRE_LIB" sourcepath="JRE_SRC">

      Maven's java:compile seems to include the same entries that Eclipse does, so I feel that this is a bug in the eclipse plugin.

      1. cp.patch
        0.6 kB
        James A. Hillyerd

        Activity

        Hide
        James A. Hillyerd added a comment -

        The attached (very trivial) patch to plugin-resources/templates/classpath.jelly fixes the problem for me, but I haven't tried it versions of eclipse other than 2.1.2.

        Show
        James A. Hillyerd added a comment - The attached (very trivial) patch to plugin-resources/templates/classpath.jelly fixes the problem for me, but I haven't tried it versions of eclipse other than 2.1.2.
        Hide
        Steve Peterson added a comment -

        Here is my workaround for this one. I am tired of waiting for the patch to be applied to the plugin. Add the following lines to your maven.xml.

        <postGoal name="eclipse:generate-classpath">
        <ant:replace file="$

        {basedir}

        /.classpath"
        summary="yes"
        token="<classpathentry kind="var" rootpath="JRE_SRCROOT" path="JRE_LIB" sourcepath="JRE_SRC">"
        value="<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER">" />
        </postGoal>

        Show
        Steve Peterson added a comment - Here is my workaround for this one. I am tired of waiting for the patch to be applied to the plugin. Add the following lines to your maven.xml. <postGoal name="eclipse:generate-classpath"> <ant:replace file="$ {basedir} /.classpath" summary="yes" token="<classpathentry kind="var" rootpath="JRE_SRCROOT" path="JRE_LIB" sourcepath="JRE_SRC">" value="<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER">" /> </postGoal>
        Hide
        dion gillard added a comment -

        The patch doesn't exist, but I've added the line to my local version of the plugin and will test it tomorrow.

        If all is ok, I will proceed with the commit.

        I'll also try it under 3.0M8

        Show
        dion gillard added a comment - The patch doesn't exist, but I've added the line to my local version of the plugin and will test it tomorrow. If all is ok, I will proceed with the commit. I'll also try it under 3.0M8
        Hide
        Brett Porter added a comment -

        any progress dion?

        Show
        Brett Porter added a comment - any progress dion?
        Hide
        dion gillard added a comment -

        Looks good to me.

        I'll catch up, bootstrap and then commit

        Show
        dion gillard added a comment - Looks good to me. I'll catch up, bootstrap and then commit
        Hide
        dion gillard added a comment -

        In 1.7

        Show
        dion gillard added a comment - In 1.7

          People

          • Assignee:
            dion gillard
            Reporter:
            James A. Hillyerd
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: