Hello Group, at first: big props for existing and your help and the plugin at first, really removes the pain from GWT builds.
I'm currently developing some enteprise app that uses a GWT-frontend. We're making use of JNDI, Spring and some other fancy stuff that creates the need for -noserver to be able to run our server application while testing new stuff in the frontend. Currently I do have a single artifact build that has everything included and am able to run mvn jetty:run with hot deploy of new code that got changed in Eclipse, a feature that is actually used really often. But since that "one big artifact" way leads to more and more problems (killing project portability and highly increasing buildtime) I took a look at the maven-gwt-sample that proposes an 3-parts split (server jar, interface jar, gwt-part that does webapp-assembling) POM architecture. I really to like that way as it sound quite reasonable and might really increase project portability, BUT: - If I need to build & jar the server part before running it together with the GWT part in the .war would that not interfere with the hot deployability? - Would I rather need to strictly devide beetween "now I'm going to debug Server Code and now GWT Code"? Any other ideas or suggestions? Thanks for your ideas and feedback :) Regards, Joti --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
