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

["Max Rydahl Andersen" <max.andersen@xxxxxxxxx>]

> 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