Tuesday, November 2, 2010

Re: Announcing GWT 2.1

This works for me but the GWTTestCases are taking forever. Each one
is starting up dev mode on a different port. I don't think that was
happening before:

[ERROR] log4j:WARN Please initialize the log4j system properly.
[INFO] Please navigate your browser to this URL:
[INFO] http://10.29.127.35:2984/{module}.JUnit/junit.html?gwt.codesvr=10.29.127.35:2980

Where {module} is the module for the GWTTestCase.

The test eventually completes but it's taking maybe 10 times as long
as it used to.

Anyone know what's going on? My configuration is below (gwt.version
is 2.1.0).

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>1.3.2.google</version>
<configuration>
<module>{module}</module> <!-- actual module name is here -->
<buildOutputDirectory>target</buildOutputDirectory>
<generateDirectory>target/generated-sources/gwt</
generateDirectory>
<runTarget>StarUI.html</runTarget>
<gwtVersion>${gwt.version}</gwtVersion>
</configuration>
<executions>
<execution>
<id>gwt-compile</id>
<phase>prepare-package</phase>
<goals>
<goal>compile</goal>
</goals>
</execution>
<execution>
<id>run-gwt-tests</id>
<goals>
<goal>test</goal>
</goals>
<configuration>
<includes>**/*_GT.java</includes>
</configuration>
</execution>
</executions>
</plugin>


On Oct 28, 11:15 pm, "arrival...@gmail.com" <arrival...@gmail.com>
wrote:
> Hi Giuseppe,
>
> I had a similar problems, and found out that late that my browser
> (i.e. chrome)  had cache the previous info, try to clean the temp data
> in the browser.
>
> Also, check whichGWTversion you specified within your plugin
> reference in pom.xml. Here is my example pom.
>
> <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>gwt-maven-plugin</artifactId>
>         <version>1.3.2.google</version>
>         <configuration>
>                 <logLevel>INFO</logLevel>
>                 <style>PRETTY</style>
>                 <gwtVersion>${gwt.version}</gwtVersion>
>                 <webappDirectory>${basedir}/war</webappDirectory>
>                 <module>${project.groupId}.isearch.ISearch</module>
>                 <runTarget>ISearch.jsp</runTarget>
>                 <copyWebapp>true</copyWebapp>
>         </configuration>
>         <executions>
>                 <execution>
>                         <id>gwtcompile</id>
>                         <phase>prepare-package</phase>
>                         <goals>
>                                 <goal>compile</goal>
>                         </goals>
>                 </execution>
>         </executions>
> </plugin>
>
> Hope this helps.
>
> Also, thank you so much for your hard work!! I had a question on
> google's "gwt-maven-plugin." First, is there documentation available
> for the different configuration available? I have questions on the
> function for  <hostedWebapp>, <webappDirectory>, <copyWebapp>? Thank
> you again~!
>
> Jay
>
> On Oct 29, 6:02 am, Giuseppe La Scaleia
>
>
>
>
>
>
>
> <giuseppe.lascal...@geosdi.org> wrote:
> > Hi all ,
> > great work. A simple question i have mymavenproject withgwt-maven-plugin
> > 1.2 version. I have upload togwt2.1.0 and for plugin at version
> > 1.3.2.google but i have the follow error
>
> > You're project declares dependency ongwt-user2.1.0. This plugin is
> > designed for version2.1-SNAPSHOT
> > java.lang.NullPointerException
> >     at
> > org.codehaus.mojo.gwt.AbstractGwtMojo.getClasspath(AbstractGwtMojo.java:220 )
> >     at
> > org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo$JavaCommand.withinScope(Ab stractGwtShellMojo.java:284)
> >     at org.codehaus.mojo.gwt.shell.CompileMojo.compile(CompileMojo.java:186)
> >     at
> > org.codehaus.mojo.gwt.shell.CompileMojo.doExecute(CompileMojo.java:178)
> >     at
> > org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo.execute(AbstractGwtShellMo jo.java:118)
> >     at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag er.java:490)
> >     at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif ecycleExecutor.java:694)
> >     at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl e(DefaultLifecycleExecutor.java:556)
> >     at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife cycleExecutor.java:535)
> >     at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai lures(DefaultLifecycleExecutor.java:387)
> >     at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def aultLifecycleExecutor.java:348)
> >     at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl eExecutor.java:180)
> >     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >     at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >     at
> > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> >     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >     at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9)
> >     at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:25)
> >     at java.lang.reflect.Method.invoke(Method.java:597)
> >     at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >     at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >     at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >     at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
> > What version must i use??
> > Thanks Giuseppe
>
> > 2010/10/28 David Chandler <drfibona...@google.com>
>
> > > You're welcome, Tim. Thanks for posting back.
>
> > > /dmc
>
> > > On Thu, Oct 28, 2010 at 4:07 PM, tim.meck...@gmail.com
> > > <tim.meck...@gmail.com> wrote:
> > > > Thanks for your quick response! I needed to update thegwt-maven-
> > > > plugin version which was previously pointing to a version that
> > > > expectedgwt-soyc-vis.
>
> > > > On Oct 28, 3:45 pm, David Chandler <drfibona...@google.com> wrote:
> > > >> Hi Tim,
>
> > > >>gwt-soyc-vis.jar is intentionally not in themavenrepo because all
> > > >> the functionality has been moved intogwt-dev.jar. You should be able
> > > >> to remove the dependency ongwt-soyc-vis from your POM.
>
> > > >> Thank you,
> > > >> /dmc
>
> > > >> On Thu, Oct 28, 2010 at 3:31 PM, tim.meck...@gmail.com
>
> > > >> <tim.meck...@gmail.com> wrote:
> > > >> > This is very exciting news.
>
> > > >> > I think I've run into a small obstacle that maybe someone could help
> > > >> > with. Upon updating mymavenbuild dependencies forgwt, my build now
> > > >> > errors on com.google.gwt:gwt-soyc-vis:jar:2.1.0 not found in themaven
> > > >> > central repo. Is this something I'm doing incorrectly?
>
> > > >> > Congratulations on the release!
> > > >> > Tim Mecklem
>
> > > >> > On Oct 28, 2:12 pm, David Chandler <drfibona...@google.com> wrote:
> > > >> >>GWT2.1is here!
>
> > >http://googlewebtoolkit.blogspot.com/2010/10/announcing-final-release...
>
> > > >> >> --
> > > >> >> David Chandler
> > > >> >> Developer Programs Engineer, Google Web Toolkithttp://
> > > googlewebtoolkit.blogspot.com/
>
> > > >> > --
> > > >> > 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<google-web-toolkit%2Bunsubs cribe@googlegroups.com>
> > > .
> > > >> > For more options, visit this group athttp://
> > > groups.google.com/group/google-web-toolkit?hl=en.
>
> > > >> --
> > > >> David Chandler
> > > >> Developer Programs Engineer, Google Web Toolkithttp://
> > > googlewebtoolkit.blogspot.com/
>
> > > > --
> > > > 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<google-web-toolkit%2Bunsubs cribe@googlegroups.com>
> > > .
> > > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > > --
> > > David Chandler
> > > Developer Programs Engineer, Google Web Toolkit
> > >http://googlewebtoolkit.blogspot.com/
>
> > > --
> > > 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<google-web-toolkit%2Bunsubs cribe@googlegroups.com>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > --
> > Giuseppe La Scaleia
> > CNR - IMAA
> > geoSDI - NSDI
> > Sviluppo Software
>
> > C.da S. Loja
> > 85050  Tito Scalo - POTENZA (PZ)
> > Italia
>
> > phone:  +39 0971427305
> > fax:      +39 0971 427271
> > mob:    +39 3804697436
> > mail:     giuseppe.lascal...@geosdi.org
> > skype:  glascaleia
>
> > web:    http://www.geosdi.org

--
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.

No comments:

Post a Comment