[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Your plug-in may be a liability if...: ACTION REQUIRED/ACTION REQUISE
|
PDE has not started enforcing these access restrictions yet.
We plan to turn it on next week.
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/07/2005 10:31 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."
Jeff,
I tried removing a package from my plugin A which was reference in plugin
B. After saving the MANIFEST.MF, there was no recompile and no flagging of
compilation problems. Only at runtime were the classes in that package not
found. Did this type of change used to work when plugin.xml contained the
exports?
I'm sure this is just temporary until M7.
-Randy
Jeff McAffer
<Jeff_McAffer@xxxxxx.
com> To
Sent by: "General development mailing list
eclipse-dev-bounces@e of the Eclipse project."
clipse.org <eclipse-dev@xxxxxxxxxxx>
cc
04/07/2005 09:49 AM Subject
Re: [eclipse-dev] Your
plug-in may be
Please respond to a liability if...:
"General development ACTION REQUIRED/ACTION
mailing list of the REQUISE
Eclipse project."
Max,
I think there is some confusion here. Plugin A contains some packages
declares exports for them. Plugin B needs some of the packages so declares
imports for them or "requires" A. If A is free to add packages to its
export list without affecting B. B does not have to change. A can remove
exports but should be mindful of API implications. Again this does not
affect B (as long as it can still be resolved).
The magic of plugins is that they know what they have (their exports) and
they know that they need (imports/requires). These lists for A are
independent of the lists for B. Are we talking about the same thing?
As for the tooling, in mere days the full power of PDE will come to bear on
the classpath and give you control over what you see. In fact, even today
the classpath that PDE manages only exposes the things that you export.
Coming is the ability to change to a strict mode where the "internal"
exports are not visible either. I think you will find that PDE's modelling
of the classpath is pretty good (Note it will not be perfect. That would
require very significant effort for marginal incremental gain).
Jeff
"Max Rydahl Andersen"
<max.andersen@xxxxxxxxx
>
Sent by: To
eclipse-dev-bounces@ecl "General development mailing list
ipse.org of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>
cc
04/07/2005 08:32 AM
Subject
Re: [eclipse-dev] Your
Please respond to plug-in may be
"General development a liability if...:
mailing list of the ACTION REQUIRED/ACTION
Eclipse project." REQUISE
> practice. What
> is the problem with that? After all, as you say in the end, you are
> developing
> plugins.
This explicit listing of packages are a pain since:
>From my understanding plugins will not be possible to access any new
packages added to some of the libraries without updating the plugin.xml
(and that is bad if users should be allowed to update the dependent
library without
needing to mess with package names)
And when you run the workbench from inside PDE you have access to all
classes/packages
in your PDE project no matter what the plugin.xml says....at least that is
my current experience.
Meaning that you will not discover any classloading issues until you start
from a total clean eclipse,
which wont happen very often while you develop.
/max
>
> _______________________________________________
>
> 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
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max@xxxxxxxxxxxxx
http://hibernate.org
JBoss Inc
max.andersen@xxxxxxxxx
http://jboss.com
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
