[
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
|
Max Rydahl Andersen schrieb:
On Thu, 07 Apr
2005 14:32:01 +0200, Max Rydahl Andersen
<max.andersen@xxxxxxxxx> wrote:
This explicit listing of packages are a pain
since:
(and here i'm explicitly talking about plugins that uses external
libraries, not inter plugin dependencies)
What exactly do you mean by external libraries? In an ideal world, all
libraries come packaged with plugins that export these libraries. Let's
say plugin A exports libraries a..z, then plugin B can declare A as
required and will automatically see A's exported libraries a..z, and B
then will be able to use them. Plugin B does not need to declare any
imported libraries, it just needs to declare that it requires plugin A.
Either you are using a Eclipse plugin architecture and have some plugin
that will be started (or an application) at the end, then things work
best with the above approach. Or you are writing something that does
not run within Eclipse, then you don't have plugins at all.
/max
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)
In the above scenario, you would just alter the libraries coming with
plugin A, and afterwards B will see these changes.
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.
I sometimes get confused with what a Project's referenced libraries are
as opposed to what its plugin's libraries are. The latter show up as
"Plugin Dependencies" in your project's classpath. You're on the secure
side of things if in your project properties' "Libraries" tab you can
only see "JRE System Library" and "Plugin Dependencies". Anything else
would not necessarily be accessible when running from a clean eclipse.
/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
--
__________________________________________________________
Dipl.-Inf. Jörg von Frantzius | artnology GmbH
| Milastr. 4
Tel +49 (0)30 4435 099 26 | 10437 Berlin
Fax +49 (0)30 4435 099 99 | http://www.artnology.com
_______________________________|__________________________
|
begin:vcard
fn;quoted-printable:J=C3=B6rg von Frantzius
n;quoted-printable:von Frantzius;J=C3=B6rg
org:artnology GmbH
adr:;;Milastr. 4;Berlin;;10437;Germany
email;internet:joerg.von.frantzius@xxxxxxxxxxxxx
title:Software Architect
tel;work:+49 (30) 443 50 99 - 26
tel;fax:+49 (30) 443 50 99 - 99
x-mozilla-html:TRUE
url:http://www.artnology.com
version:2.1
end:vcard