Darren Janeczek wrote:
> First,
> Is there a more formal area to post bugs for Qt Jambi Eclipse Integration?
>
Hi, Darren.
You can use the bug reporting form:
http://www.qtsoftware.com/bugreport-form
Set product as "Qt Jambi" and function as "Other".
I will register the bug from this e-mail myself, so no need to do it in
this case =)
>
> This chunk of XML will be inserted repeatedly for each subsequent import,
> which gives me the impression it was a quick fix, acceptable for most normal
> cases.
> My problem with this automatic insertion is that projects that have no UI
> components are receiving this build instruction, which really spam-hammers
> eclipse's autobuild/refresh functionality when you have a lot of projects in
> your workspace. It gets worse when other members of the team don't have their
> Qt-Jambi set up.
>
> Need to check if this juicBuilder contribution exists.
> Need to check if there are any ui files present.
> Need to deal with case when ui files are added to a project without the
> juicBuilder contribution.
> Anything else?
>
You should be able to disable juic for your project by opening its
properties and going to the "Builders" page. Just uncheck the box for
the JUIC builder.
I agree that adding juic to every project could be considered very
intrusive, and it was done as a compromise, because juic is required for
many projects, and the resulting errors if it were missing would be hard
to debug for novice users.
This goes for new projects, however. Adding the juic builder to existing
projects that are being imported into the workspace is clearly a bug, so
I will make a task to fix it for the next Qt Jambi release.
> Lastly,
> If no one is available, please show me to the code repository / where I can
> sign up.
>
>
Unfortunately the Eclipse Integration is not open source, and there is
no public code repository.
-- Eskil
_______________________________________________
Qt-jambi-interest mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
