Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6995068

fastdebug builds don't generate populated jdk*debug*tar bundles

XMLWordPrintable

    • b114
    • generic
    • generic
    • Verified

        When a full release build is split into a "product" build and a "fastdebug" build, to run both in parallel, you end up with empty jdk*debug*tar bundles:

        jdk-7-ea-linux-amd64-debug.tar.gz
        jdk-7-ea-linux-i586-debug.tar.gz
        jdk-7-ea-solaris-amd64-debug.tar
        jdk-7-ea-solaris-i586-debug.tar
        jdk-7-ea-solaris-sparc-debug.tar
        jdk-7-ea-solaris-sparcv9-debug.tar
        jdk-7-ea-windows-amd64-debug.tar
        jdk-7-ea-windows-i586-debug.tar

        This is because the "product" build generates all the .tar bundles in the install forest and reaches over to the "fastdebug" build to generate the jdk*debug.tar bundles.

        The self extracting jdk*debug*.sh (solaris) and jdk*debug*bin (linux) are also empty when the product and fastdebug are built in parallel. But these bundles are likely obsolete and should no longer be generated, as they aren't shipped or used internally.

              pbhat Pranav Bhat (Inactive)
              katleman David Katleman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: