Community
Participate
Working Groups
Since 9, -Xbootclasspath and -Xbootclasspath/p are illegal, while -Xbootclasspath/a is still allowed. While most of this is correctly implemented in JDT, a few details might deserve a final closer look: Illegal use is logged since bug 522696, but BootpathTest.testPrependBootpath() demonstrates that API still allows to create entries with IJavaLaunchConfigurationConstants.ATTR_BOOTPATH_PREPEND even at 9+ OTOH, the UI no longer provides any means to mark classpath entries as bootstrap, because at 9+ the category Bootstrap Entries is gone (in favor of Module Path vs. Class Path). My original use case (bug 562556) manipulates these things via API, so I'm not sure of any use case where users might need to explicitly set -Xbootclasspath/a Finally, I'm not sure if it's OK that AbstractJavaLaunchConfigurationDelegate.getBootpath(ILaunchConfiguration) answers null, where BootpathTests.testEmptyBootpath() originally expects an empty arry.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
For a launch Configuration or module definition, through Eclipse UI the bootpath can not be set. But through APIs if someone adds bootstrap to the classpath, there is nothing to stop.
