No, with hindsight, it makes sense :) It was just that it references web.xml that caused my confusion - but... at least now something will show up on google if anyone else hits the issues!
Thanks, Ian 2008/11/5 Charlie Collins <[EMAIL PROTECTED]> > > I would say that we should improve the error message if it's in any > way misleading (I hate when error messages are either pointless, or > lead you in the wrong direction), but it looks like it already says: > > "Embedded error: module file null" > > Not sure we can improve that ;). > > On Nov 5, 11:02 am, "Ian Christian" <[EMAIL PROTECTED]> wrote: > > 2008/11/5 Célio <[EMAIL PROTECTED]> > > > > > > > > > I don't know if that's your case, but that error occurred to me when I > > > forgot to define my app module, something like: > > > > Thanks, I figured it out in the end. I wasn't aware of the -X switch, > > which shows lots of useful debugging. > > Turns out it was because I didnt' have a .gwt.xml file anywhere in my > > project. I knew I didn't have one, but the error I found a little > > misleading, and I wasn't looking at the right things to solve it. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
