Repo consolidation update: new jcheck published, jdk10/master populated!

Martin Buchholz martinrb at google.com
Thu Sep 14 18:17:32 UTC 2017


On Thu, Sep 14, 2017 at 11:03 AM, Erik Joelsson <erik.joelsson at oracle.com>
wrote:

> Hello Martin,
>
> On 2017-09-14 10:22, Martin Buchholz wrote:
>
>> I tried out jdk10 master for a test drive.  Notes:
>>
>> I had to amend my jdk build tree version detector as follows:
>>
>>
>> sed_if_file_found() {
>>    if [[ -f "${@: -1}" ]]; then sed -E "$@"; fi
>> }
>>
>> major() {
>>    # works with jdk10 post-repo consolidation
>>    sed_if_file_found -n \
>>      -e 's/^DEFAULT_VERSION_MAJOR=([0-9]+)$/\1/p' \
>>      "make/autoconf/version-numbers"
>>    # works with jdk8
>>    sed_if_file_found -n \
>>      -e 's/^DEFAULT_VERSION_MAJOR=([0-9]+)$/\1/p' \
>>      -e 's/^JDK_MINOR_VERSION=([0-9]+)$/\1/p' \
>>      "common/autoconf/version-numbers"
>>    # works with jdk7
>>    sed_if_file_found -n -e 's/JDK_MINOR_VERSION *= *([0-9]+)$/\1/p' \
>>      "jdk/make/common/shared/Defs.gmk"
>> }
>>
>> (Is there a blessed way to do this?)
>>
> Not that I can think of. The directory moved because having a "common" no
> longer made sense, so we decided to put everything build related in "make".
>
> What is the use case for that script? I've never not known what source I'm
> dealing with. Just curious.
>
>
You always want to be up to date, so you hg tupdate all your forests, and
then rebuild them all, and you want to be able to do that with a single
script, without keeping track of which one is which version.

rebuild-openjdk ~/ws/*


More information about the jdk10-dev mailing list