|author||Stephan Herrmann <firstname.lastname@example.org>||Thu Jan 28 21:37:03 2021 +0100|
|committer||Vikas Chandra <Vikas.Chandra@in.ibm.com>||Thu Mar 31 23:57:25 2022 -0400|
Bug 526011 - PDE should provide an abstraction above annotation-configuration in .classpath * introduce new manifest header Eclipse-ExportExternalAnnotations * if set to true, resolved entries in Required-Plugins will define their annotationPath equal to the plugin location This suffices to help JDT/Core to use these annotations for null analysis, if .eea files are shipped with the plug-in jar. We even have content assist for the new header :) Change-Id: I84643bc57d3da9f5a8f50d61da4ea82f8cd9cac9 Signed-off-by: Stephan Herrmann <email@example.com> Reviewed-on: https://git.eclipse.org/r/c/pde/eclipse.pde.ui/+/175466 Tested-by: Vikas Chandra <Vikas.Chandra@in.ibm.com> Reviewed-by: Vikas Chandra <Vikas.Chandra@in.ibm.com>
Thanks for your interest in this project.
The PDE project the Eclipse tooling to develop plug-ins and OSGI bundles.
Contributions to PDE are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the [How to Contribute] 1 page on the team wiki.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
You need Maven 3.3.1 installed. After this you can run the build via the following command:
mvn clean verify -Pbuild-individual-bundles
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.