I would suspect the support JAR in that case too then, just as a transitive dep. I don't understand how the Mojo setting could do it though. I will look into it further when I get a chance.
On May 1, 1:13 pm, Karim Qazi <[email protected]> wrote: > I could not get the plugin to use strictly 1.6.4 GWT without changing > the Mojo. This DOES work if you set the gwtHome env variable and > install 1.6.4 of GWT manually however if you want to use strictly > dependencies from the POM you have to do what I'm talking about. > > I deleted my local maven repo multiple times and every time it would > download 1.5.3 GWT lib's until I changed this in the Mojo. I even > re-build the maven-googlewebtoolkit-support module which has 1.5.3 set > as the GWT version which I initially thought was the issue, but not > until I changed the Mojo did it all work. > > I basically brought the entire trunk into IntelliJ and did a search > for 1.5.3 and changed everything in POM's, re-installed locally, ran > builds in offline mode to ensure nothing except what was on my local > got picked up and still no luck till I changed the Mojo. > > Again the plugin does work as stated IF you set the gwtHome env > variable but doesn't if you use strictly gwt pom dependencies. > > On Fri, May 1, 2009 at 7:29 AM, Charlie Collins > > <[email protected]> wrote: > > > You don't have to change the Mojo to override the default. > > > Also the "properties" gwtVersion is a convenience that has nothing to > > do with what GWT-Maven actually uses. Its the gwtVersion in the > > CONFIGURATION that gets applied (or the default from the Mojo is used > > if you don't specify). > > >http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plug... > > > <configuration> > > <compileTargets> > > <value>com.totsp.sample.Application</value> > > </compileTargets> > > <runTarget>com.totsp.sample.Application/ > > Application.html</runTarget> > > <logLevel>INFO</logLevel> > > <style>DETAILED</style> > > <noServer>false</noServer> > > <extraJvmArgs>-Xmx512m</extraJvmArgs> > > <gwtVersion>${gwtVersion}</gwtVersion> > > </configuration> > > > On Apr 30, 2:59 pm, "[email protected]" <[email protected]> wrote: > >> /** > >> * Set the GWT version number - used to build dependency paths, > >> should match > >> * the "version" in the Maven repo. > >> * > >> * @parameter default-value="1.5.3" > >> */ > >> private String gwtVersion; > > >> The above is causing gwt 1.5.3 to be the version that the plugin > >> depends on . I had to set this to 1.6.4 in AbstractGWTMojo and re- > >> install to my local maven reop to get my project that uses GWT to work > >> with all 1.6.4 dependencies. > > >> This looks like it may be a bug as no matter what version you specify > >> in your pom with the > >> <properties> > >> <gwtVersion>1.5.3</gwtVersion> > >> </properties> > > >> The plugin.xml always has 1.5.3 set in it's configuratoin. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
