|Re: How to disable jdt UI contributions with org.eclipse.activities? [message #515645 is a reply to message #515590]
||Fri, 19 February 2010 10:54
| Patrick Oppermann
Registered: July 2009
I need a "simplified" version of my application where the Java
functionalities are not supposed to be visible (or even available for
the user), but my own plugins (some of which depend on jdt) still need
to be active.
However, the mistery has been solved. The runtime workspace I was using
still had the jdt views persisted in its metadata. Creating a new
runtime workspace did the trick. The expression that eventually worked
for me is .*/org\.eclipse\.jdt\..*
Am 19.02.2010 14:41, schrieb Daniel Megert:
> Patrick Oppermann wrote:
>> Hello everyone,
>> for my eclipse application, I defined a custom activity using the
>> org.eclipse.activities extension point in order to filter out all UI
>> contributions that I don't need. Basically it works fine, except for
>> the contributions made by org.eclipse.jdt.ui. I defined a pattern
>> binding like this:
>> I also tried several variations of the regular expression like
>> ".\/org\.eclipse\.jdt\.ui\..*" etc., but none of them caused my
>> application to disable any JDT button, view or menu entry.
>> Are there any special issues to keep in mind when trying to filter
>> JDT-related UI stuff?
> Note that the SDK download already has a capability that disables JDT
> and it works just fine. Also, why do you download a package with JDT if
> you don't need it?
>> Patrick Oppermann
Powered by FUDForum
. Page generated in 0.37967 seconds