I see. Believe me it's not your fault. GWT is a mature technology, and there are tons of articles and tutorials that were written for different versions in different contexts, and it's hard to know which one is more accurate, mainly when you're starting with the technology.
I use Eclipse too, and sometimes Eclipse really mess the things up when dealing with different plugins at same time (in this case, GWT and Maven plugins). I'm used to it, but it took some time to understand the nuances of working with GWT on it. Before you start, you have to think about 2 parallel dependency trees: Maven's and GWT's. GWT have its own way to define which modules should be compiled and which module depends on which one. That's your Module.gwt.xml. On top of that there is which libraries you need to compile the Java project (now including not only the client side, but server as well). That's where Maven comes in. The thing is, you can create a GWT project without Maven. You can import all the jars you need by hand if you prefer. Or use another build tool. Its your choice. But you can't get rid of you Module.gwt.xml. So let's start by it. Paste you Module.gwt.xml here so we can take a look at it and see if there's something wrong =) Since you're new to GWT and Maven, I'd say it's a good strategy to make GWT work alone before entering in the Maven world. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
