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

[Martin Buchholz]

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?)

Looks like other scripts will need adjustment for the new directory layout.

---

If I do
hg log $(find -name AtomicInteger.java))
I only get one commit

But hg log -f works well, and file locations have changed, so this is as
expected.

---


On Wed, Sep 13, 2017 at 9:27 PM, joe darcy <joe.darcy at oracle.com> wrote:

> Hello,
>
>
> On 9/12/2017 5:04 PM, joe darcy wrote:
>
>> Hello,
>>
>> We've run into some jcheck failures associated with the consolidated
>> repo. We're working on resolving them, which may require a jcheck update to
>> add items to the white list, etc. Since the consolidation process alters
>> the changeset hashes, the existing white list entries do to apply to the
>> corresponding changesets in the consolidated repo.
>>
>> Cheers,
>>
>> -Joe
>>
>
> A new version of jcheck has been published and installed on the OpenJDK
> Mercurial server. You can refresh your local copy from
>
> http://hg.openjdk.java.net/code-tools/jcheck/dist/raw-file/tip/jcheck.py
>
> The initial push to the new consolidated master repo
>
>     http://hg.openjdk.java.net/jdk10/master
>
> has completed! Semantically, the sources are equivalent to those in the
> non-consolidated JDK 10 b23.
>
> The repo is currently closed to pushes other than those related to the
> consolidation. We're still working on updating our infrastructure and
> validating builds and tests of the consolidated repository. There may be a
> few small additional changes made to the repo as part of the preparation
> for opening it up again.
>
> We'll have another tagging of the post-consolidation state as b24 before
> general development resumes.
>
> Cheers,
>
> -Joe
>