-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: None
-
Component/s: infrastructure
-
b26
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8056573 | emb-9 | Unassigned | P2 | Resolved | Fixed | b26 |
| JDK-8063173 | 8u45 | Mikael Vidstedt | P2 | Resolved | Fixed | b01 |
| JDK-8054559 | 8u40 | Mikael Vidstedt | P2 | Closed | Fixed | b02 |
| JDK-8071118 | emb-8u47 | Mikael Vidstedt | P2 | Resolved | Fixed | team |
For testing purposes the JDK build system has support doing a bootcycle build - a second build phase where the JDK is rebuilt using the JDK from the first phase. It used to be possible to control the bootcycle build by means of the SKIP_BOOT_CYCLE make file variable when invoked from jprt, but that accidentally got dropped when the logic to call configure was moved out of Jprt.gmk.
The SKIP_BOOT_CYCLE logic needs to be added again.
The SKIP_BOOT_CYCLE logic needs to be added again.
- backported by
-
JDK-8056573 Support SKIP_BOOT_CYCLE=false when invoked from JPRT
-
- Resolved
-
-
JDK-8063173 Support SKIP_BOOT_CYCLE=false when invoked from JPRT
-
- Resolved
-
-
JDK-8071118 Support SKIP_BOOT_CYCLE=false when invoked from JPRT
-
- Resolved
-
-
JDK-8054559 Support SKIP_BOOT_CYCLE=false when invoked from JPRT
-
- Closed
-
- relates to
-
JDK-8029797 Let jprt run configure when building
-
- Resolved
-