>> First, > Is there a more formal area to post bugs for Qt Jambi Eclipse Integration? > > Here is my problem: > When the Qt Jambi Eclipse Integration plugins are enabled in eclipse, I've > noticed that whenever a project (of any kind) is imported into a workspace, > the following is automatically added to the .project file in the > <buildSpec> section: > > <buildCommand> > <name>com.trolltech.qtjambi.juicBuilder</name> > <arguments> > </arguments> > </buildCommand> > > 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? > One more, deal when you add a ui file in a normal java project. Generate a lot of crashes. > Lastly, > If no one is available, please show me to the code repository / where I can > sign up. > > Thanks. > Darren Janeczek > _______________________________________________ > Qt-jambi-interest mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
_______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
