Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3989

Set the Java 5 compilation path based on the Java 6 compilation path if a Java 5 environment can't be found but a Java 6 environment can be

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.5.1.1
    • 10.5.1.1
    • Build tools
    • None
    • Patch Available

    Description

      This will make the build even more flexible. Probably involves the following changes:

      1) Relaxing the requirement in PropertySetter that a Java 5 JDK must exist

      2) Having PropertySetter look for a Java 6 JDK (and set java16compile.classpath accordingly) just as PropertySetter looks for a Java 5 JDK today

      3) Changing the setCompilerProperties target in the master build script so that it

      a) requires that java15compile.classpath or java16compile.classpath is set (it's ok for both to be set)

      b) sets java15compile.classpath to ${jdbc3stubs}:${java16compile.classpath}

      Attachments

        1. derby-3989-01-aa-optionalJava5.diff
          10 kB
          Richard N. Hillegas
        2. derby-3989-01-ab-optionalJava5.diff
          12 kB
          Richard N. Hillegas
        3. derby-3989-01-ac-optionalJava5.diff
          15 kB
          Richard N. Hillegas
        4. derby-3989-02-aa-dontUseJava6LibsWithJava5Compiler.diff
          4 kB
          Kristian Waagan

        Issue Links

          Activity

            People

              rhillegas Richard N. Hillegas
              rhillegas Richard N. Hillegas
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: