Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 235058

Summary:	[spec] javadoc for JavaCore#setComplianceOptions needs improvement
Product:	[Eclipse Project] JDT	Reporter:	Maxime Daniel <maxime_daniel>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	markus.kell.r
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Maxime Daniel

2008-06-02 03:32:14 EDT

I20080530-1730
The javadoc forJavaCore#setComplianceOptions starts with:
	 * Sets the default's compiler options inside the given options map according
	 * to the given compliance.

which is almost meaningless.
Having discussed with Olivier and read the code, I believe that the original intent was to set in the provided map the values of the sole options that were impacted by the compliance, deriving their values as the compiler would do 'by default' when provided the compliance only (that is, without any other option than JavaCore.COMPILER_COMPLIANCE being specified by the caller). Since some of these options definitely have a non-mandatory flavor when considering some compliance levels (aka JavaCore.COMPILER_PB_ASSERT_IDENTIFIER for 1.3 or 1.4), rendering the effective behavior in a concise documentation may turn out to be a bit challenging.

Comment 1 Markus Keller

2014-10-06 09:44:54 EDT


*** This bug has been marked as a duplicate of bug 263769 ***