-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b34
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8083028 | emb-9 | Staffan Larsen | P2 | Resolved | Fixed | b34 |
| JDK-8067535 | 8u45 | Staffan Larsen | P2 | Resolved | Fixed | b01 |
| JDK-8066510 | 8u40 | Staffan Larsen | P2 | Closed | Fixed | b18 |
| JDK-8070923 | emb-8u47 | Staffan Larsen | P2 | Resolved | Fixed | team |
The complete motivation is in this email thread: http://mail.openjdk.java.net/pipermail/hotspot-dev/2014-September/015244.html
"We propose a move to a Hotspot development model where we can do both
hotspot and jdk changes in the hotspot group repos. This will require a
fully populated JDK forest to push changes (whether hotspot or jdk
changes) through JPRT. We do not expect these changes to have much
affect on the open community, but it is good to note that there can be
changes both in hotspot and jdk code coming through the hotspot
repositories, and the best practise is to always clone and build the
complete forest."
"We propose a move to a Hotspot development model where we can do both
hotspot and jdk changes in the hotspot group repos. This will require a
fully populated JDK forest to push changes (whether hotspot or jdk
changes) through JPRT. We do not expect these changes to have much
affect on the open community, but it is good to note that there can be
changes both in hotspot and jdk code coming through the hotspot
repositories, and the best practise is to always clone and build the
complete forest."
- backported by
-
JDK-8067535 Disable JPRT submissions from the hotspot repo
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-