|
Re: Newbie: 3rd Party Plug-ins WTP1 [message #161652 is a reply to message #161324] |
Wed, 22 February 2006 17:55 |
David Williams Messages: 722 Registered: July 2009 |
Senior Member |
|
|
On Tue, 21 Feb 2006 04:58:17 -0500, Pranas <pranas.baliuka@cablenet.lt> wrote:
> Hi *WTP* Gurus,
>
> I have problems with restrictions defined in plug-ins (e.g. Apache libs)
> provided by WTP 1.0. And current WTP 1.0 approach for using plug-ins with
> 3rd party code breaks existing functionality (in my environment).
> Are there some known work arounds?
I believe there are some preferences that let you control if this is an
error or warning? Otherwise, you'd have to hand-hack the manifest.mf file,
in the plugin, until fixed.
>
> Can 3rd party plug-ins provided by TWO updated to let access all packages?
> Would it be bug or feature request?
>
Kind of a bug, kind of a feature reqquest (I'd suggest opening as bug).
By default, it is the Eclipse Convention to "export"
*everything*, and mark it as "x-internal" if not really intended to
be used by clients.
The "feature request" part is that we have not really considered doing
this "x-internal" part for 3rd party code, but its a reasonable request.
Thanks.
|
|
|
Powered by
FUDForum. Page generated in 0.01488 seconds