[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
[news.eclipse.platform] Re: Problems after upgrading from Eclipse 3.1 to 3.2 with external libs
From
: Paul Webster <
pwebster@xxxxxxxxxx
>
Date
: Tue, 28 Nov 2006 08:31:57 -0500
Newsgroups
:
eclipse.platform
Organization
: EclipseCorner
User-agent
: Thunderbird 1.5.0.7 (X11/20060911)
AFAIK this difference is an added tooling check to help cut down on the "It works in eclipse but fails when I export it" problems.
Eclipse plugins need to get info from other plugins ... i.e. in runtime if it's not in a plugin, then it's not visible*
You can use info like
http://wiki.eclipse.org/index.php/Plug-in_Development_Environment
to create plugins for your external jars or include them in a common library plugin.
*there are a very few exceptions to this, almost all dangerous.
Later, PW
Follow-Ups
:
[news.eclipse.platform] Re: Problems after upgrading from Eclipse 3.1 to 3.2 with external libs
From:
Mirco Dunker
References
:
[news.eclipse.platform] Problems after upgrading from Eclipse 3.1 to 3.2 with external libs
From:
Mirco Dunker
Prev by Date:
[news.eclipse.platform] Re: [Activities] failure when in separate plug-in
Next by Date:
[news.eclipse.platform] Re: Enable and disable SynchronizeModelAction added in P_TOOLBAR_MENU
Previous by thread:
[news.eclipse.platform] Problems after upgrading from Eclipse 3.1 to 3.2 with external libs
Next by thread:
[news.eclipse.platform] Re: Problems after upgrading from Eclipse 3.1 to 3.2 with external libs
Index(es):
Date
Thread