Re: [eclipse-dev] Your plug-in may be a liability if...: ACTION REQUIRED

[Randy Hudson <hudsonr@xxxxxxxxxx>]

The generated manifest.mf  exports
the default package.  Shouldn't this be removed (for performance reasons)
when possible?

-randy

Wassim Melhem <wassimm@xxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx

04/05/2005 11:39 AM

Please respond to
"General development mailing list of the Eclipse project."

To	eclipse-dev@xxxxxxxxxxx
cc
Subject	[eclipse-dev] Your plug-in may be a liability if...: ACTION        REQUIRED/ACTION REQUISE

All Eclipse teams,

If you have not already done so, please plan on creating a manifest.mf
for
your plug-in for NEXT WEEK's I-build.

To do so:
1. Open your plugin.xml/fragment.xml in the PDE manifest editor.
2. In the Plug-in Content section of the Overview page, click on the
'Create an OSGi bundle manifest' link.
This will create a manifest.mf file, trim down your plugin.xml and  update
your build.properties.
3. Save and check in the changes into HEAD.
DONE!

At that point, you will notice that the first three pages of the manifest
editor have changed and you will be able to explore many of the cool
runtime capabilities that you probably did not even know they existed.


Please note that:

1. If your plug-in does not have a manifest.mf, you are (and always have
been) an overhead for the runtime, and you are (and always have been)
nothing short of a liability to PDE.
So startup, launching, etc. and many of your day-to-day self-hosting
activities will become significantly faster once you convert.

2. PDE tooling makes the conversion process transparent, and your
development process afterwards will not be affected in any way.
For example, when you use the plug-in editor to edit your plug-in's
manifest files, PDE takes care of writing the data to the right files.

3. We are NOT suggesting that a plug-in will not work in 3.1 if it doesn't
have a manifest.mf.
PDE will continue to make your plug-in experience as pleasant as it has
always been if you don't have one.

4. As of next week's I-build, the default option to create one with a
manifest.mf in the New Plug-in Project wizard will be turned on, as this
is
the recommended format for 3.1.


If you have any questions, please send them to this list.


To sum up:

If your plug-in does not have a manifest.mf, it ain't happening.



_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev