EVALUATION
http://hg.openjdk.java.net/lambda/lambda/hotspot/rev/a9831b955a0a
|
|
|
EVALUATION
http://hg.openjdk.java.net/hsx/hotspot-comp/hotspot/rev/a9831b955a0a
|
|
|
EVALUATION
http://hg.openjdk.java.net/hsx/hotspot-gc/hotspot/rev/a9831b955a0a
|
|
|
EVALUATION
http://hg.openjdk.java.net/hsx/hotspot-main/hotspot/rev/a9831b955a0a
|
|
|
EVALUATION
http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/a9831b955a0a
|
|
|
EVALUATION
We'll leave the default as jdk7 for now, since most projects are currently destined for some 7 update release. However, I'll restructure the file to make changing defaults simple and remove unused targets.
|
|
|
EVALUATION
7070061 added the basic support for using "-release jdk8" by adding all the jprt.*.jdk8.* properties.
This CR is proposing to hard-wire the default release in jprt.properties to be jdk8 instead of whatever was specified on the -release option to JPRT submit.
There has been some debate on whether this is actually a necessary or correct change to make. The most recent JPRT update allows for the -release option to be visible in the jprt.gmk file but I still don't think we should be hard wiring this value in jprt.properties in the workspace. As it stands once this is hard-wired then you can only get a jdk8 build unless you edit the file before the submission.
|
|
|
EVALUATION
This bug already has a changeset associated with it; see previous note.
That changeset is for the jdk8/build repo so I doubt that it was for a
hotspot change.
Also, there is this bug:
7070061 4/4 Adjust Hotspot make/jprt.properties for new JDK8 settings
which was fixed in HSX-22-B01 so I'm thinking that this bug is already
fixed, but that should be verified.
|
|
|
EVALUATION
Fix in progress.
|
|
|
EVALUATION
http://hg.openjdk.java.net/jdk8/build/rev/fd8615098a54
|
|
|