On Fri, Oct 16, 2009 at 10:00 AM, Tom Schindl <[email protected]> wrote: > Hi Francis, > > First of all thank you for doing this work. I don't know if you already > did this but the last time I tried to hack on Qt-Jambi my main problem > was that the Java-Sources are not in a dedicated directory and my > Eclipse couldn't really deal with this. > > What I'd like to see is that QT-Jambi uses a default project layout > structure (e.g. the one maven uses src/main/java, src/main/resources) > this would allow us to add qt-jambi to the maven repo in future quite > easily. >
Well, the "default project layout" structure is quite some unfathomable notion, because it's entirely dependent on what tools you use :p But the separation of files is done already (all individual Java modules are in java/src/<themodulenamehere>). There are a few problems with the "total integration approach" though: * The first is OSInfo.java and Version.java; both are used by ant-qtjambi.jar and qtjambi.jar. For now, they are both in a dedicated, two-class jar which is far from being ideal. I have some ideas to get rid of that jar. * The second problem is that you actually need to generate Java sources to build qtjambi at all. This is the role of the generator. AND the Java sources you'll be able to generate directly depend on what Qt components you have available (yes, you don't even have the choice - I intend to fix that too). Now, if only I could add ant-contrib as a build dependency, the job would be much easier :p -- Francis Galiegue, [email protected] "It seems obvious [...] that at least some 'business intelligence' tools invest so much intelligence on the business side that they have nothing left for generating SQL queries" (Stéphane Faroult, in "The Art of SQL", ISBN 0-596-00894-5) _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
