I haven't yet played with the new project structure, but speaking with 1.4 and 1.5 experience, I agree with Martin - that it is somewhat difficult to build GWT projects with "enterprise continuous integration systems", such as Maven (which, in particular, depends on a certain project structure). A little more configurability in where source can be located may be the best solution to this issue.
On Feb 10, 4:01 am, maku <martin.k...@gmx.at> wrote: > Hi, > > from my point of view it is nice that GWT 1.6 brings a more > transparent project structure. > > BUT, what we really need is a concept which fits into enterprise > development strategies. > > e.g. I'm not able to see how using maven and continous integraton and > developing can be achievend in a painless way. > - running application in hosted mode maybe with an own server (- > noserver mode)) > - working with more than one project > - clean seperation of generated and not generated code > - and so on... > > Yes, I know it is possible to handle this stuff and we did it ... But > we spent already so much time on this infrastructural things. And I > guess we are not alone.... > And to get a simple to use infrastructure is almost impossible. > > Regards, > Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
