OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

heads-up: Java 1.6 (6.0) in the works

Date: Thu, 8 Dec 2005 15:57:24 -0800
From: Danek Duvall <danek dot duvall at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com
Subject: heads-up: Java 1.6 (6.0) in the works

The Nevada CBE will be moving from Java 1.5 to 1.6 in January.  No exact
date has been determined, as it depends on several unknown factors,
including when the 1.6 beta will ship, and when all the other
consolidations are ready for it.  But it should be ready roughly mid- to
late January.

With that in mind, all gatelings who own Java code need to test against the
new JDK.  Any bugs you find related to the new JDK, whether it's a JDK bug
or an ON bug, should be marked with the keyword "s11-cbe-jdk16", so that
the Java folks can track the issues.

(If you own Solaris-bound Java code outside ON, or know someone else that
does, you should test that code, or pass this message on.  If you don't
know whether another consolidation will be affected by the switch, please
contact the appropriate gatekeeper or c-team lead.)

I have already done a compile test on ON; only one component fails, and a
bug has already been filed against that.  But functionality testing still
needs to be done.  If there are any problems, they should be considered
bugs against the JDK.

You can get new JDK packages from:

    /net/koori.sfbay/onestop/jdk/6/promoted/latest/bundles/solaris-sparc/pkgarchive

where "sparc" can be substituted with "sparcv9", "i586", and "amd64" for
64-bit sparc, x86, and 64-bit x86 packages, respectively.

Ready-to-run binaries are available from

    /net/koori.sfbay/onestop/jdk/6/promoted/latest/binaries/solaris-sparc

with the same substitutions.  Note that the 64-bit extensions are not
necessary for ON to build (or run, I believe).

New builds typically come out every Thursday afternoon, available in the
above locations.

Adding the new packages to your system will not overwrite old packages or
create new instances of old packages, as the package names are different
(SUNWj6* vs SUNWj5*).  The new packages will not overwrite old files, or
switch the default Java to the new version.

For those who don't want to add new packages to their systems, you can test
the new JDK by setting

    JAVA_ROOT=/net/koori.sfbay/onestop/jdk/6/promoted/latest/binaries/solaris-<whatever>

in the build's environment, either by putting it in your nightly env file,
or by setting it in your shell environment and ensuring that you do a "make
-e".

Any questions and follow-ups should be directed at the gatekeepers and at
Dave Katleman.  I'll clarify on the list as necessary.

I'll send out another heads-up once we have a firm date on the switch.

Thanks,
Danek