Build folk,
Is there a way we could put a file in each repo containing the ids of
the minimum required changeset of other repos?
It would then surely be a simple consistency check to verify that all
the repos involved in a build meet the minimum level of functionality.
-- Jon
-------- Original Message --------
Subject: Heads up: Integrating lambda-related changes into jdk8/jdk8
Date: Tue, 16 Jul 2013 13:42:04 -0600
From: Alejandro E Murillo <alejandro.muri...@oracle.com>
Organization: Oracle Corporation
To: jdk8-...@openjdk.java.net
Later today I plan to push the hs25-b41 snapshot into jdk8 master [1]
<http://hg.openjdk.java.net/jdk8/jdk8/>,
along with the fix for 8016281
<http://bugs.sun.com/view_bug.do?bug_id=8016281>. This push includes
lambda-related changes that will
create lambda-related incompatibilities with class files compiled with
earlier
JDK 8 versions. See [2]
<http://mail.openjdk.java.net/pipermail/lambda-dev/2013-July/010449.html> for
more details.
Once the changes have been integrated, the hotspot, langtools and jdk
repos must match - i.e., either all must have these changes or not have
any of them.
A JDK with mismatched repos may build, but some lambda-related functionality
might not work properly (again, see [2]
<http://mail.openjdk.java.net/pipermail/lambda-dev/2013-July/010449.html> for
details of the symptoms).
After we integrate, If you do pull, make sure to pull all: hotspot,
langtools and jdk,
and to build all
[1] http://hg.openjdk.java.net/jdk8/jdk8/
[2] http://mail.openjdk.java.net/pipermail/lambda-dev/2013-July/010449.html
Thanks
--
Alejandro
