Re: no clue on: module may need to be recompiled - help

Well, I thought I had the problem worked around, but, darn it, it came
back. Then I re-read through all of the posts of the folks who tried
to help me and it turns out that Thomas Broyer's post pointed to the
exact problem. Specifically, when doing a clean before my build I
clean out the spurious *.nocache.js file in src/main/webapp user maven-
clean-plugin. This did the trick. Thanks Thomas!

On Apr 27, 8:34 am, cri <chuck.irvine...@gmail.com> wrote:
> I've managed to work around the problem. The main thing that made the
> difference was importing the initial project into eclipse using the
> native eclipse command "Import -> Existing project" rather than the
> command that I believe is provided by m2eclipse, i.e. "Import... /
> Existing maven project".
>
> It would be a great thing if either Google would officially add maven
> support or if the gwt-maven-plugin guys could get their plugin working
> seamlessly with GPE. The plugin does work very nicely for the most
> part. Its just that GPE/Eclipse integration hasn't been their focus.
>
> On Apr 27, 5:55 am, "dolly khemani." <khemani.do...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > I suggest that you clean your project then compile again and check

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.