|
|
|
Re: plug-in loading classes question [message #448431 is a reply to message #448428] |
Mon, 24 April 2006 14:43 |
|
Christian Gesswagner wrote:
> Right, there is a dependency, but how can I tell the plugin to look in its
> own classes first?
you cannot. That's not the way plugin classloading works, and you can't
fool around with it.
An example of eclipse NLS stuff:
org.eclipse.ui.workbench has the WorkbenchMessages NLS class. It also
defines the messages.properties class, which provides it's basic messages.
Then they use a fragment, hosted off of org.eclipse.ui.workbench, to
provide the messages_de.properties in the same package. Fragments are
sucked into the classpath of the host plugin exactly as if they were
part of the host plugin. Then it can find the language when it's changed.
You can't replace something that's already in the classpath, but you can
add the extra bits.
Later,
PW
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
|
|
|
|
Powered by
FUDForum. Page generated in 0.03743 seconds