Bug 135217 - Compiler class constructor change in 3.2
Summary: Compiler class constructor change in 3.2
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 RC1   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-06 04:13 EDT by David Audel CLA
Modified: 2006-04-13 12:33 EDT (History)
1 user (show)

See Also:

Attachments
Proposed fix (25.59 KB, patch)
2006-04-06 11:50 EDT, David Audel CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Audel CLA 2006-04-06 04:13:07 EDT 
Some eclipse clients are using the org.eclipse.jdt.internal.compiler.Compiler class and noticed that its constructor has changed from 3.2M4 to 3.2M5 (added the statementsRecovery boolean parameter).

Even if it is an internal class it would be better to keep this 'internal' API compatible with older version (3.2M4).
Comment 1 David Audel CLA 2006-04-06 11:50:13 EDT 
Created attachment 37900 [details]
Proposed fix
Comment 2 Philipe Mulet CLA 2006-04-06 13:48:47 EDT 
+1 for 3.2RC1
Comment 3 David Audel CLA 2006-04-07 05:10:46 EDT 
Fix released.

I marked 3.2M4 constructors as deprecated.
I changed other constructors to use CompilerOptions instead of the Map of settings and boolean parameters.
Comment 4 Maxime Daniel CLA 2006-04-13 12:33:09 EDT 
Verified for 3.2 RC1 using Build id: I20060413-0010.
Old constructors have been reintroduced as deprecated.