Qt-jambi-interest Archive, May 2007
eclipse plugin builder
Message 1 in thread
Hello,
I've recently installed QT Jambi and the Eclipse plugin. I noticed that there is a problem with the properties of a widger, but that's a known issue.
What I also noticed, is that the juic builder is added to all Java projects, even when no QT Jambi is used in a project. Not that much a problem, but a project takes at least twice as long to build. I disabled the builder ('cause I don't need it in most projects), and it stays disabled. However, the next time Eclipse starts, another builder is added and enabled. Currently I have at least five QT Jambi builders for every project, 4 disabled and 1 enabled. Is there a way to tell the Eclipse plugin "not to do this"? And is there a way to remove the disabled builders?
Version information: both QT Jambi and Eclipse are at the latest "stable" versions.
Regards,
Erik.
Message 2 in thread
On Friday 25 May 2007 14:39, Erik Verbruggen wrote:
> Hello,
>
> I've recently installed QT Jambi and the Eclipse plugin. I noticed that
> there is a problem with the properties of a widger, but that's a known
> issue.
>
> What I also noticed, is that the juic builder is added to all Java
> projects, even when no QT Jambi is used in a project. Not that much a
> problem, but a project takes at least twice as long to build. I disabled
> the builder ('cause I don't need it in most projects), and it stays
> disabled. However, the next time Eclipse starts, another builder is added
> and enabled. Currently I have at least five QT Jambi builders for every
> project, 4 disabled and 1 enabled. Is there a way to tell the Eclipse
> plugin "not to do this"? And is there a way to remove the disabled
> builders?
>
> Version information: both QT Jambi and Eclipse are at the latest "stable"
> versions.
>
> Regards,
> Erik.
Hi Erik
We have overlooked the problem with the juic builder, and we will fix it. I
don't think there is a way for you to turn this miss behaving 'adding' off.
The only solution I have for you is to have to separate eclipse
installations, one with the plugins and one without.
Thanks for finding and reporting this problem. :-)
Best Regards,
Håvard F