<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 15, 2011, at 2:27 AM, Steve Poole wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Times; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">Primarily then the objective of having multiple repositories is to improve developer productivity and component stability.<br><br></span></span></blockquote><div><br></div>And also facilitate the ability to distribute some components to multiple projects outside the jdk or multiple jdks.</div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Times; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">I don't know how much cross-repo changes go on. It would seem that if that is minimal then the next logical step would be to<br>remove the source for the repos you're not working on and just have the binaries instead. Do you see that as a worthwhile goal?<br></span></span></blockquote></div><br><div>When doing partial builds, there is a ALT_JDK_IMPORT_PATH (import jdk) setting which is supposed to point to</div><div>a jdk built image (one with a bin, lib, include, jre, etc. layout). This should be a very recent jdk7 build</div><div>image, and is normally the last promoted jdk build (which changes weekly with each promotion).</div><div>That is where previously built components come from, see the jdk/make/java/redist/Makefile for details.</div><div><br></div><div>This ALT_JDK_IMPORT_PATH setting has taken on various names over the years, you will also see</div><div>ALT_HOTSPOT_* variables in the jdk repository makefiles.</div><div><br></div><div>So for partial builds, you need a ALT_BOOTDIR (boot jdk) and also a ALT_JDK_IMPORT_PATH</div><div>to get the components that you are not building.</div><div><br></div><div>For OpenJDK, once you have a complete forest build, you can save the j2sdk-image directory somewhere,</div><div>point ALT_JDK_IMPORT_PATH at that area, and you should be good to go for doing partial builds</div><div>in the hotspot or jdk repositories. The langtools, jaxp, jaxws, and corba repositories are fairly standalone</div><div>and don't result in a complete built jdk image when built by themselves.</div><div><br></div><div>See:</div><div><a href="http://blogs.sun.com/kto/entry/anatomy_of_the_jdk_build">http://blogs.sun.com/kto/entry/anatomy_of_the_jdk_build</a></div><div><a href="http://blogs.sun.com/jjg/entry/building_javac_for_jdk7">http://blogs.sun.com/jjg/entry/building_javac_for_jdk7</a></div><div><br></div><div>-kto</div></body></html>