Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
P3
-
Resolution: Fixed
-
Affects Version/s: 9
-
Fix Version/s: 9
-
Component/s: infrastructure
-
Labels:None
-
Subcomponent:
-
Resolved In Build:b170
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8180667 | 10 | Magnus Ihse Bursie | P3 | Resolved | Fixed | b09 |
JDK-8180525 | 9.0.4 | Magnus Ihse Bursie | P3 | Resolved | Fixed | b01 |
Description
Now --with-jtreg works like this:
* --without-jtreg will explicitly disable jtreg.
* --with-jtreg=<jtreg home> will use the specified directory, and will do sanity checks that it is indeed a jtreg home pointed to, and not a binary.
* When no option is given, we try to locate jtreg using JT_HOME from the environment, and, failing that, by finding the jtreg executable in the path and deriving a JT_HOME from that. If not found, jtreg will be disabled.
* --with-jtreg (with no arguments) will try to locate jtreg automatically as described above, but if it fails, it will abort configure.
Attachments
Issue Links
- backported by
-
JDK-8180525 --with-jtreg is broken for many use cases
-
- Resolved
-
-
JDK-8180667 --with-jtreg is broken for many use cases
-
- Resolved
-
- duplicates
-
JDK-8020779 --with-jtreg should probe for jtreg on the $PATH
-
- Closed
-
- relates to
-
JDK-8180897 Explicit --with-jtreg path not expanded
-
- Resolved
-