| [dtp-pmc] Using manifest files |
Our not using manifest files has turned into a widespread discussion --
take a look at:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=130598
So, let's just make the move before 0.7 and be done with it. David
Williams has helped out with the following tip:
1. Open plugin.xml in the PDE editor for a plug-in without a manifest file
2. In the "Overview" page, click on the "create an OSGI bundle manifest"
link (see attached image)
3. The result of (2) is a manifest file being created in the plug-in
project
4. Technically, if plugin.xml is then empty, it could be deleted. If you
want to do so, you need to send an email to the CVS admin (
webmaster@xxxxxxxxxxx) with the CVS module/plug-in name/file name to do
this. Alternatively, you can just leave plugin.xml there for the moment.
5. Be sure to add the new manifest file to CVS
6. Test that the plug-in still works as expected.
As I mentioned before, 24 out of 43 DTP 0.7 plug-ins already have manifest
files. The ones not using manifest files are spread across the three
projects. I would like to make this update by the end of tomorrow (for
Friday's build), and I am happy to take care of this. Please let me know if
any committer would rather make this change for their particular plug-in.
Regards,
John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.
http://dataplat.blogspot.com/
(See attached file: convert_to_manifest.JPG)Attachment:
convert_to_manifest.JPG
Description: JPEG image
