Community
Participate
Working Groups
The deprecated version of the method internally calls the new version using as arguments CompilerOptions.VERSION_1_3 for the source and compliance level. This is the indication as to what an API client should pass for these values since there is no documentation to this effect (!!). Non-internal constants and better docs are required on this method to make the API usable.
Actually, JavaCore#VERSION_x_y should be used. But I agree that the Javadoc is not clear on this point. Changing bug title to reflect real problem.
It would also be a good idea to change the constant used in the deprecated method to use this constant. When I do deprecation updates I usually follow whatever migration strategy is adopted inside the deprecated method (why I initially used the wrong consts).
Created attachment 154131 [details] Proposed fix
Released for 3.6M5. Verification needs to be done by checking the javadoc.
Verified for 3.6M5 by code inspection.