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

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.5.1.1
    • Fix Version/s: 10.5.1.1
    • Component/s: Build tools
    • Labels:
      None
    • Issue & fix info:
      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

        Issue Links

          Activity

            People

            • Assignee:
              rhillegas Richard N. Hillegas
              Reporter:
              rhillegas Richard N. Hillegas

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment