I don't use m2eclipse plugin in eclipse. I do *mvn eclipse:eclipse *and import the project in eclipse and works fine. The one thing that I must *do by hand *in eclipse is enable GWT project nature. To do this, in project properties, in google category option Google Web Toolkit press *Apply.* * *
2011/10/27 cri <[email protected]> > You are correct. I was referring to the combination of eclipse/gwt/ > maven. And from what I gather, the version of m2e updated for Indigo > has caused all kinds of breakage of existing maven plugins (when used > with Indigo). Personally, I'm to the point of believing that you are > better off without using maven for gwt projects until the situation > improves. > > On Sep 23, 12:24 pm, Hilco Wijbenga <[email protected]> wrote: > > On 23 September 2011 09:53, cri <[email protected]> wrote: > > > > > The uptick post is very outdated. It will only confuse folks I'm > > > afraid. A much better place to start is the link I posted. (http:// > > > code.google.com/p/google-web-toolkit/wiki/WorkingWithMaven). > > > Developing GWT in conjunction withMavenhas IMHO always been error > > > prone and tricky. It does seem like the GWT team is giving a little > > > more importance to this than they have in the past. The new Indigo / > > >mavenintegration has thrown a wrench in things to some extent. > > > > I don't think that's entirely correct. > > > > Mavenworks fine with GWT and has been since (IIRC) 2.1. What possibly > > doesn't work fine is *Eclipse* +Maven+ GWT. I have no problems > > (other than the usual) but I run builds on the command line (where > > they belong) and use Eclipse for simple compiling and > > editing/refactoring/formatting/et cetera. > > > > Having said that, there are certainly a number of issues. GWT's > > approach to JARs/project management is not quite optimal. It requires > > existing JARs to be changed to create one-offs that don't exist > > anywhere else (AFAIK). Furthermore, these JARs are then all dumped > > together in a few big ueber JARs. This breaksMaven'sdependency > > management and creates classpath problems. Luckily, the fallout > > doesn't seem too bad. It would be great if this could be improved (and > > work is being done in this area). Of course, it would be even better > > if GWT usedMavenitself instead of Ant... ;-) > > > > By the way, I have not been able to get Indigo to run properly at all. > > It keeps breaking on updates so I'm still on Helios. I do get the > > impression that theMavenplugins (there's more than one) are at the > > heart of the issue but I have not delved in any deeper. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" 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/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
