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

Need to allow underscore version strings in build version

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 1.4.1
    • 1.4.1
    • infrastructure
    • None
    • hopper
    • generic
    • generic



      Name: dm26566 Date: 02/15/2002


      The current j2se version string only support development releases. To support
      CTE update releases, an update version string should be added.

         JDK_UPDATE_VERSION

      if defined, the value should be appended to the version strings for use
      in bundle names and version binary display.\ ( % java -version ).

      ======================================================================

      Per Amy Wang:


      Requirements:
      The update release builds can be triggered by defining
      JDK_UPDATE_VERSION.

      . The update release build in RE requires the following:
        1. JDK_VERSION is 1.4.1_nn where nn is JDK_UPDATE_VERSION.
        2. The RELEASE and FULL_VERSION variables should remain the same
           in the makefile, but should show the version string 1.4.1_nn.
        3. java -version and java -fullversion output
           For FCS milestone:
              157 % ./java -version
              java version "1.4.1_01"
              Java(TM) 2 Runtime Environment, Standard Edition (build
      1.4.1_01-b04)
              Java HotSpot(TM) Client VM (build 1.4.1_01-b04, mixed mode)

              158 % ./java -fullversion
              java full version "1.4.1_01-b04"

           For EA milestone:
              19 % ./java -version
              java version "1.4.1_01-ea"
              Java(TM) 2 Runtime Environment, Standard Edition (build
      1.4.1_01-ea-b02)
              Java HotSpot(TM) Client VM (build 1.4.1_01-ea-b02, mixed mode)

              20 % ./java -fullversion
              java full version "1.4.1_01-ea-b02"

        4. Docs and Forte cobundle are not needed in update releases.
           There should be a way to disable docs and Forte cobundle
           build when update release build is triggered.
        5. The version part of the bundles should show 1_4_1_nn and
           the remaining parts should keep following the naming
           convention.
           Example:
             j2re-1_4_1_01-fcs-bin-b01-solsparc-01_mar_2002.sh


      . Additional requirements for JPSE's nightly build:
        1. java -version and java -fullversion output
              This should be a nightly timestamp with the following
              format. Note that there is no reference to the particular
              update version.

          % ./java -version
          java version "JPSE_1.4.1_20020301"
          Java(TM) 2 Runtime Environment, Standard Edition (build
      JPSE_1.4.1_20020301)
          Java HotSpot(TM) Client VM (build JPSE_1.4.1_20020301, mixed mode)
          % ./java -fullversion
          java full version "JPSE_1.4.1_20020301"

          2. Other than the above requirement, JPSE does not have any special
             requirement for the bundle names etc.
             Example: It looks clumsy but OK.
        
      j2re-1_4_0_01-internal-bin-JPSE_1.4.0_20020301-solsparc-01_mar_2002.sh

          3. During the build, the vars that are set in RE and JPSE:
                         Update releases RE JPSE
                         ================== ====
         MILESTONE ea/fcs not set
         BUILD_NUMBER b01, b02 .... not set
         JDK_UPDATE_VERSION nn nn

      ###@###.### 2002-03-07

            vjayaramsunw Vijayan Jayaraman (Inactive)
            dmcduffisunw Dale Mcduffie (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: