https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220
Complete the configuration of PDE API Tooling in the Papyrus Main
and Developer Tools projects, including:
* adding the API Analysis nature and builder to .project where it was missing
* adding a new menu action in the dev tools Project Management menu to ensure
that all Oomph version-management projects in the workspace have API analysis also
* fixing API version analysis problems, mostly by upversioning bundles to 2.0
but also applying API filters in some cases where it seems appropriate
* implementing project-level API Analysis preferences for warning severity of
missing @since doc tags (the default is error) and adding it to the Oomph
project preferences management
Change-Id: I3f5fad20ffc7bb66eec0abbb86b5cc52aacb1ff1

https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220
Implement version management: PDE API Tooling and Oomph
Version Management.
Introduce two new plug-in projects to manage versioning
using Oomph:
* org.eclipse.papyrus.releng.main.release for the Main
bundles and features
* org.eclipse.papyrus.releng.dev.release for the Dev Tools
Add new menu actions to the Dev Tools:
* main menu bar:
* synchronize POM and manifest versions
* "Configure" context menu on bundle projects and MANIFEST.MF
* optimize bundle dependencies and re-exports
* update dependency version ranges to match current workspace
and PDE target
Remove obsolete menu actions from the Dev Tools:
* main menu bar:
* Set all Papyrus feature versions
* Set all Papyrus plug-in versions
* Set versions of all Papyrus dependencies in Papyrus plug-ins
Fix versioning errors reported by PDE and Oomph. Ensure proper
version ranges consistent with latest build target.
Optimize the dependencies of all Papyrus Main bundles and Dev Tools.
Remove version- and reexport-checking tests in the BundlesTests that
are now not needed because, on the one hand, we now implement discrete
bundle versioning (managed by PDE/Oomph) and on the other, we now use
re-exports properly to ensure classpath consistency in clients of a
bundle's API.
Thorough overhaul of the "project editors" API, including:
* rationalize the API interfaces
* refactor the all-in-one PluginEditor class from the customization
bundle to the project-editors bundle
* update clients in the Customization and DSML Validation components
* fix a bunch of operations that didn't work
* add missing operations required by the new Dev Tools actions
* complete some unimplemented APIs
* add a comprehensive JUnit test suite covering all of the
project-editors API
Change-Id: I6a699d93909f61099226ceb994140f03ea99a70f

https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220
Fix the actual problem with the dev build's bundle dependency
resolution, which is that the infra.gmfdiag.css.debug bundle's
parent module was not the dev releng module of which it was a child.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220
Fix build failure to resolve bundles in referenced p2
repositories by restoring the missing <groupId> elements in
the POMs which, as it turns out, are not inherited from the
parent module, despite what the m2e validator says.
Change-Id: I62dacc9c70c940d28c3c02e1e35c8f874a7d3df0

compilation
https://bugs.eclipse.org/bugs/show_bug.cgi?id=459566
Add Tycho compiler's <useProjectSettings> to the plug-in management in the main top
POM to ensure that each project's build preferences are respected.
This does require removing a few {@link}/@see references to restricted API in doc
comments to work around a bug in Tycho (459554).
A great many plug-in projects using 1.6 source constructs (mostly @Override of
abstract methods) failed to declare 1.6 requirement either in the BREE, or the
classpath/compiler settings, or both.
Change-Id: Ia73b592fff8d46eaf0bc628b6e21d1e758ff0c64