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

mustang bundles contains 1_6_0 instead of 6_0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 6
    • 6
    • infrastructure
    • None
    • mustang
    • generic
    • generic

      Name :- vj102386 Date :- 2004-30-08
      -----------------------------------------------------------------------

      Currently all the mustang bundles has 1_6_0, we should have 6_0.


      Some email threads:-
      =====================


       Mark Reinhold wrote:

      >>Date: Thu, 26 Aug 2004 14:52:33 -0700
      >>From: ###@###.###
      >>
      >>
      >
      >
      >
      >>Vijayan Jayaraman wrote:
      >>
      >>
      >>>Please advise me on this:-
      >>>
      >>>I can take care about changing the string 1.6.0 to 6.0 in the email
      >>>part/directory name...etc.
      >>>
      >>>But should we change the bundle name as well to 6.0 ?. If so then we
      >>>need to make changes into the makefile.
      >>>
      >>>
      >>Our naming czar (Brian) might have more to say, but I agree that
      >>everything that is not tied to interface issues, like -version
      >>/-fullversion should get changed.
      >>
      >>Yes, they should be changed to 6.0.
      >>
      >>
      >
      >Careful... Directory names are interfaces too. The multiple-JRE feature
      >in Tiger will break if we start naming install directories jdk6.0 instead
      >of jdk1.6.0. If we absolutely must change the names of the install
      >directories then we'd also have to change the JRE lookup algorithm in all
      >of the current update releases (1.4.2_x and 1.5.0_x).
      >
      >- Mark
      >
      >
      If I might be allowed to interpret Graham's email.

      Everything that we haven't decided to keep as 1.6.0 should start to be switched over to 6.0. We did a "good enough" job of this in the Tiger release but for Mustang we should be thorough. I think this needs to include internal only stuff like our project web pages or directories where builds get posted on internal servers. As I've mentioned before, I think this is necessary in order to train our tongues to say "6.0". And that's necessary if we want this change to stick.

      Of course, if this is not an accurate interpretation, Graham please correct me.

      Brian.



      >
      >
      >>>>Graham Hamilton wrote:
      >>>>
      >>>>
      >>>>>Happiness!
      >>>>>
      >>>>>By the way, before we get too far down the Mustang path, we
      >>>>>should change all the product numbering to consistently be "6.0".
      >>>>>
      >>>>>In a few places within the product and with the "java -version"
      >>>>>and "java -fullversion" flags it will still return the string "1.6.0",
      >>>>>for application compatibility. But when we talk about the product
      >>>>>or create bundle names or directories we should talk about it as
      >>>>>JDK 6.0
      >>>>>
      >>>>>

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

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: