RVM
  1. RVM
  2. RVM-95

Switch to building Classpath with javac (stop download of ecj?)

    Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1000
    • Component/s: Infrastructure: Build
    • Labels:
      None
    • Number of attachments :
      0

      Description

      We now use Classpath 0.95 as our default. Classpath 0.95 has a build option of --with-javac meaning it can be compiled without ecj, this means we can remove downloading ecj from our build. There's a possible issue in that the Classpath build may run out of memory with javac, so we may need to run the Classpath configure with --with-javac="javac -J-Xmx512M -target 1.5".

        Issue Links

          Activity

          Hide
          Ian Rogers added a comment -

          A related note, ecj 3.3 has just been released so we can bump:
          "http://download.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/ecj.jar"
          in builds/components/ecj.xml to:
          "http://fullmoon.torolab.ibm.com/downloads/drops/R-3.3-200706251500/ecj.jar"

          Show
          Ian Rogers added a comment - A related note, ecj 3.3 has just been released so we can bump: "http://download.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/ecj.jar" in builds/components/ecj.xml to: "http://fullmoon.torolab.ibm.com/downloads/drops/R-3.3-200706251500/ecj.jar"
          Hide
          Ian Rogers added a comment -

          Enabling patch committed as r13792.

          Show
          Ian Rogers added a comment - Enabling patch committed as r13792.
          Hide
          Andrew John Hughes added a comment -

          With Classpath 0.96.1, just --with-javac should be sufficient as the memory requirement will be automatically dealt with if the javac found supports that option.

          Show
          Andrew John Hughes added a comment - With Classpath 0.96.1, just --with-javac should be sufficient as the memory requirement will be automatically dealt with if the javac found supports that option.
          Hide
          Ian Rogers added a comment -

          Currently we are downloading Classpath 0.97 but compiling with ecj 3.2. We need the ecj dependency because:

          • all JDK 1.5s can't compile Classpath 0.97 due to a bug in javac, in particular our PowerPC set ups are relying on JDK 1.5 VMs awaiting a more stable 1.6 VM release
          • the ecj that is installed on Fedora and OpenSuSE, by default, is the broken 3.3.0 version that creates a broken Classpath
          Show
          Ian Rogers added a comment - Currently we are downloading Classpath 0.97 but compiling with ecj 3.2. We need the ecj dependency because: all JDK 1.5s can't compile Classpath 0.97 due to a bug in javac, in particular our PowerPC set ups are relying on JDK 1.5 VMs awaiting a more stable 1.6 VM release the ecj that is installed on Fedora and OpenSuSE, by default, is the broken 3.3.0 version that creates a broken Classpath

            People

            • Assignee:
              Unassigned
              Reporter:
              Ian Rogers
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: