JDK-6627364 : javac needs Float and Double on the bootclasspath even when not directly used
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2007-11-08
  • Updated: 2011-05-18
  • Resolved: 2011-05-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 Other
6u10Fixed 7 b34Fixed OpenJDK6Fixed
Related Reports
Relates :  
JDK-6627366 - javac needs Cloneable and Serializable on the classpath even when not directly used
Relates :  
JDK-6627362 - javac generates code that uses array.clone, which is not available on JavaCard
Description
javac needs Float and Double on the classpath, even when float and double values are not being used.
Comments
EVALUATION Will consider synthesizing the classes if they are not available on the bootclasspath.
06-12-2007
EVALUATION Float and Double are required when checking if the unboxing conversion JLS 3, 5.1.7. The difficulty here is that checking for unboxing is part of the third phase of method resolution, JLS3 15.12.2, and 15.12.2.4, so even overload resolution may indirectly use Float and Double.
08-11-2007
EVALUATION Should work to have empty classes for Float and Double on the bootclasspath for compilation.
08-11-2007
EVALUATION The problem occurs in the unboxing code, where the compiler looks to see if a target type is a subtype of any of the box types.
08-11-2007