JDK-4821353 : new warning "finally cannot complete normally" should not be enabled by default
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 1.4.2,1.4.2_02,5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,solaris_8,windows_2000
  • CPU: generic,x86
  • Submitted: 2003-02-20
  • Updated: 2004-03-30
  • Resolved: 2003-10-24
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.
Other
1.4.2_05 05Fixed
Related Reports
Duplicate :  
JDK-4973040 - Only in 1.4.2, javac output warning by default when "return' in finally block
Duplicate :  
JDK-4908268 - Complier generates warning if you throw an exception inside a finally block
Description
The warning described by 4814715 should not be enabled by default.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_05 generic tiger tiger-beta FIXED IN: 1.4.2_05 tiger-beta INTEGRATED IN: 1.4.2_05 tiger-b26 tiger-beta
14-06-2004
PUBLIC COMMENTS ...
10-06-2004
EVALUATION As per JAT. ###@###.### 2003-02-20 For 1.4.2_05, this bug is fixed by disabling undesired warning with commenting out the problematic lines because introducing new javac options as -Xlint is not permissible in update releases. ###@###.### 2004-03-11
11-03-2004