| Re: [eclipse-dev] Your plug-in may be a liability if...: ACTION REQUIRED/ACTION REQUISE |
I'm not an API guy so I'm in no position to comment on the best practices
of using internals as a way to establish API.
I am a plug-in guy though. So if your plugin.xml is empty after the
conversion and your plug-in will not contribute extensions/extension
points, then off with its head.
Wassim.
Randy Hudson
<hudsonr@xxxxxx.c
om> To
Sent by: "General development mailing list
eclipse-dev-bounc of the Eclipse project."
es@xxxxxxxxxxx <eclipse-dev@xxxxxxxxxxx>
cc
04/06/2005 11:37 Subject
AM Re: [eclipse-dev] Your plug-in
may be a liability
if...: ACTION
Please respond to REQUIRED/ACTION REQUISE
"General
development
mailing list of
the Eclipse
project."
Internal packages always have always been exported. There are plenty of
reasons to export internal. It's one way to establish future API.
After migrating, if the plugin.xml is empty, can it just be deleted?
-Randy
Wassim Melhem
<wassimm@xxxxxxxxxx>
Sent by: To
eclipse-dev-bounces@ec "General development mailing list
lipse.org of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>
cc
04/06/2005 11:03 AM
Subject
Re: [eclipse-dev] Your plug-in
Please respond to may be a
"General development liability if...:
mailing list of the ACTION REQUIRED/ACTION
Eclipse project." REQUISE
When you convert, all the packages that were made visible to clients via
export * will be listed in the Export-Package header (both internal and
API)
Therefore, no existing client will be broken.
As we are starting to enforce our API using the new Runtime/JDT/PDE
technologies, why would you even want to expose a newly created internal
package to clients?
Therefore, John's statement stands in that, when it comes to addition of
new packages, you only have to worry about new API packages.
Wassim.
_______________________________________________
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