Community
Participate
Working Groups
Eclipse project best practice seems to be moving toward requiring API baselines. For one thing, such requirement would help with issues like bug 357779 where there is no reliable way to ensure that a stupid Mac developer doesn't try to use Java 1.6 API. This would require the following changes to each project: 1. Adding API tools builder and nature to each .project file. See below. 2. Adding an org.eclipse.pde.api.tools.prefs file to .settings. (See enclosed to follow.) <projectDescription> <name>org.eclipse.mylyn.modeling.emf.core</name> <comment></comment> <projects> </projects> <buildSpec> ... <buildCommand> <name>org.eclipse.pde.api.tools.apiAnalysisBuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> ... <nature>org.eclipse.pde.api.tools.apiAnalysisNature</nature> </natures> </projectDescription>
Created attachment 204237 [details] Suggested API prefs settings.
Yes, this should be enabled for all Mylyn projects. If it is not enabled for the modeling project please fix that. Which API tools settings are you suggesting to change specifically?
Reopening accidentally closed bug.
(In reply to comment #2) > Which API tools settings are you suggesting to change specifically? I mean which settings in the attached file deviate from the defaults.
INVALID_REFERENCE_IN_SYSTEM_LIBRARIES=Error The default is "Ignore" which obviously makes it useless for this case. The only thing is that it will require people to install the environment descriptions, but they should probably have them there anyway.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn