On Feb 20, 2012, at 5:33 AM, Henri Gomez wrote: > 2012/2/20 Edvard Wendelin <edvard.wende...@oracle.com>: >> Hi, >> >> jdk7u-dev is the primary development forest for non-hotspot changes for 7 >> updates. This is the forest individual developers use. >> >> jdk7u is the stable master forest where the integrators push changes from >> different integration areas (hotspot-main, jdk7u-dev, CPU releases etc). >> Fixes going into the master should be well tested, which is why the >> integrator run extra testing before pushing changes from integration area to >> master. The Oracle JDK developer preview builds published on jdk7.java.net >> are built from the master forest. > > Ok thanks to clarify. > > To build OSX OpenJDK, I used jdk7u-dev. May be time to go to jdk7u > > BTW, I notice a change between them relative to OSX build. > > OSX stuff (Contents/Home) moved from j2sdk-image to j2sdk-bundle and > from j2re-image to j2re-bundle last week on jdk7u-dev > It still under j2sdk-image and from j2re-image on jdk7u > > Which one will be the good one ?
Once the next integration from jdk7u-dev to jdk7u happens, both will be copying the final output into j2sdk-bundle and j2re-bundle. This was done because the current scheme prevented you from doing a self-hosted build because some of the tool binaries were getting moved out from underneath the bootdir during the build, causing it to fail. -- Scott K. ---------------------------------------- Scott Kovatch scott.kova...@oracle.com Santa Clara/Pleasanton, CA
