--
You received this message because you are subscribed to the Google Groups "Codehaus Mojo gwt-maven-plugin Users" group.
To post to this group, send email to codehaus-mojo-gwt-...@googlegroups.com.
To unsubscribe from this group, send email to codehaus-mojo-gwt-maven-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
Try with
File -> Import -> Maven -> Existing Maven Projects
Perso I always use this (and tested the archetype with this :-) )
> For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
>
>
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
There is a problem with the archetype. It defaults to using 2.1.0 not 2.1.1 and it doesn't use the ${gwtVersion} but 2.1.0. You're probably getting errors because you have different versions of GWT on your classpath.change your pom to use 2.1.1 instead of 2.1.0 and I think you should be gtg.
--
You received this message because you are subscribed to the Google Groups "Codehaus Mojo gwt-maven-plugin Users" group.
To post to this group, send email to codehaus-mojo-gwt-...@googlegroups.com.
To unsubscribe from this group, send email to codehaus-mojo-gwt-maven-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
--
You received this message because you are subscribed to the Google Groups "Codehaus Mojo gwt-maven-plugin Users" group.
To post to this group, send email to codehaus-mojo-gwt-...@googlegroups.com.
To unsubscribe from this group, send email to codehaus-mojo-gwt-maven-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
Does your gwt.XML inherit the test module?
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
but i thought this problem is solved by m2e extras (gwt support)? Or
what does m2e extras do for gwt support? (i saw no difference after
installing it).
--
--
You received this message because you are subscribed to the Google Groups "Codehaus Mojo gwt-maven-plugin Users" group.
To post to this group, send email to codehaus-mojo-gwt-...@googlegroups.com.
To unsubscribe from this group, send email to codehaus-mojo-gwt-maven-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
i can't believe that this is a bug - screenshots on the website
clearly show gwt.xml in resources path.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
--
You received this message because you are subscribed to the Google Groups "Codehaus Mojo gwt-maven-plugin Users" group.
To post to this group, send email to codehaus-mojo-gwt-...@googlegroups.com.
To unsubscribe from this group, send email to codehaus-mojo-gwt-maven-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.
thx for this background information
in this running configuration, where was the gwt.xml placed and how
> The archetype has been set based on a running configuration, where I was
> able to run modules from Eclipse with a right-click "run as...".
was .../resources filter set?
that means that your plugin allways generatet gwt.xml in .../
> This may not work anymore with newer m2eclipse and GEP, this may also not
> work depending on various configurations (it only was tested on my desktop).
resources? And older m2eclipse versions probably didn't filter all .../
resources?
agreed as long as it's no option to place gwt.xml into .../java -path
> Hope we'll get someting more stable ASAP but this will only work if we get a
> better integration between GEP and M2E
(like david chendlers examples did)