Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321650 - Add project specific compiler settings
Summary: Add project specific compiler settings
Status: CLOSED FIXED
Alias: None
Product: Graphiti
Classification: Modeling
Component: Core (show other bugs)
Version: 0.7.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 0.7.0   Edit
Assignee: Michael Wenz CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-03 15:59 EDT by Karsten Thoms CLA
Modified: 2010-10-07 03:07 EDT (History)
1 user (show)

See Also:
michael.wenz: iplog+

Attachments
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 Karsten Thoms CLA 2010-08-03 15:59:22 EDT 
When importing the Graphiti plugins into a workspace with Java 1.5 by default the @Override annotations for interface method implementations are marked as error. Of course this could be resolved by changing the workspace setting, but this would not be necessary when project specific settings are enabled and stored.
This happens for the plugins
- org.eclipse.graphiti
- org.eclipse.graphiti.examples.common
- org.eclipse.graphiti.ui

To change this open the project settings, "Java Compiler" settings. Then check "Enable project specific settings" and "Use compliance level from execution environment 'JavaSE-1.6' on the Java Build Path".

Check in the ./settings/org.eclipse.jdt.core.prefs file.
Comment 1 Michael Wenz CLA 2010-08-11 04:12:45 EDT 
I set the compliance level as described by Karsten and checked in the settings file for all Graphiti projects

-Michael
Comment 2 Michael Wenz CLA 2010-09-08 09:44:42 EDT 
Added version and target milestone
Comment 3 Michael Wenz CLA 2010-10-07 03:07:52 EDT 
Part of 0.7.0 release