Thanks -- makes sense, although I hate the idea of having to do a "mvn package" everytime before running in host mode. If I punt on the maven directory structure and go with the "war" directory can I shorten my edit-debug cycle? What do most maven users do?
On Jul 15, 6:25 pm, Daniel <[email protected]> wrote: > The GWT Maven plugin deviates from the standard Maven directory > structure by default, to accommodate the Google Plugin for Eclipse's > default directory structure. If you want to use the standard Maven > directory layout (with the static resources for your War file in src/ > main/webapp instead of the war directory) with the Google Plugin for > Eclipse, there are some things you need to make sure of. > > 1. In the GWT Maven Plugin <configuration>, add <hostedWebapp>$ > {project.build.directory}/${project.build.finalName}</hostedWebapp>. > That will cause the plugin to use target/my-example-project-1.0.0- > SNAPSHOT (or whatever your project is called) instead of the war > directory. > 2. Configure the Google Plugin for Eclipse to use src/main/webapp > instead of war > 3. Before you can run the project in hosted mode, you'll need to run > mvn package, to copy your static resources from your GWT public > package and src/main/webapp to your hosted mode directory. You'll only > need to do this the first time. > > On Jul 16, 5:17 am, David Vree <[email protected]> wrote: > > > The documentation is very complex, but ultimately it provided the > > answer. I needed to configure the maven-war-plugin to filter (e.g. > > copy) the files from my webapp directory to the war directory. I > > accomplished this via the following snippet in my module level POM: > > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-war-plugin</artifactId> > > <configuration> > > > > <webappDirectory>war</webappDirectory> > > </configuration> > > </plugin> > > > Thanks for the help. The debugging stop points don't work, but I'll > > start a new thread on that.... > > > On Jul 15, 11:19 am, SalvadorDiaz <[email protected]> wrote: > > > > Hi, > > > > You might want to take a look at the GWT maven plugin documentation > > > (there are lots of useful tips): > > > >http://mojo.codehaus.org/gwt-maven-plugin/ > > > > Hope that helps, > > > > Salvador > > > > On 15 juil, 03:35, David Vree <[email protected]> wrote: > > > > > Manually moving index.html to the WEB-INF directory solver the 404 > > > > problem. But there is still something wrong. > > > > > The pop-up window I get with the regular GWT application doesn't pop- > > > > up in my application. And the debugging stop point I added for > > > > onModuleLoad doesn't catch. > > > > > On Jul 14, 6:40 pm, Thomas Broyer <[email protected]> wrote: > > > > > > On 14 juil, 19:25, David Vree <[email protected]> wrote: > > > > > > > Total GWT newbie here trying to get the first app up and running. > > > > > > I'm > > > > > > using Eclipse 3.5.2 and have created and run the sample app you get > > > > > > with New->Google->Web Application. The app and the GWT plugin for > > > > > > Eclipse all work great. > > > > > > > Now I am trying to add a GWT client module to my multi-module maven > > > > > > project that already contains various server maven-modules. I used > > > > > > the the "gwt-maven-plugin" archetype to create the module and the > > > > > > directory structure seems fine, however, I cannot run in hosted > > > > > > mode. > > > > > > > When launching the debug web application I get an error in the > > > > > > console: > > > > > > > [WARN] No startup URLs supplied and no plausible ones found -- > > > > > > use -startupUrl > > > > > > > I noticed that the working application used the -startupUrl argument > > > > > > to the launch and so I added "-startupUrl index.html" to mine but > > > > > > when > > > > > > browsing to that location with firefox I get a 404. > > > > > > > http://127.0.0.1:8888/index.html?gwt.codesvr=127.0.0.1:9997 > > > > > > > I picked index.html as the URL because the archetype created that > > > > > > file > > > > > > in the "src/main/mywebapp/" directory -- which also contains my WEB- > > > > > > INF directory. I'm not sure this part of the directory structure > > > > > > is > > > > > > correct. Another potential problem is that the "war" directory in > > > > > > this module does not contain the index.html. So perhaps the > > > > > > resources > > > > > > are not getting copied correctly. Any guidance here is > > > > > > appreciated! > > > > > > I'm primarily a GWT user, and only started using Maven very recently. > > > > > My project uses a "standard GWT project" layout where there's a war/ > > > > > folder at the "top level", and "standard Maven project" otherwise > > > > > (src/ > > > > > main/java, src/test/java, etc.) > > > > > It works with the Eclipse plugin because this one expects (by > > > > > default!) a war/ folder with some HTML (or JSP) page in it. > > > > > Unfortunately, I can't really tell if it works "in Maven", as I > > > > > haven't really tried a "mvn gwt:compile" (I'm prototyping and haven't > > > > > yet committed enough things to our repo to know if it'd work on our > > > > > new Hudson CI server) > > > > > For now, I configured my Maven project following: > > > > > - gwt-maven-plugin > > > > > docs:http://mojo.codehaus.org/gwt-maven-plugin/user-guide/war-folder.html > > > > > - GWT 2.1 Spring Roo integration (which generates a Maven project; > > > > > note that I haven't ever used Spring Roo,just looking at the SVN > > > > > repo)https://fisheye.springsource.org/browse/spring-roo/addon-gwt/src/main... > > > > > > FWIW, I'm using the 1.3.1.google version of the gwt-maven-plugin that > > > > > you can find in the GWT repo > > > > > athttp://google-web-toolkit.googlecode.com/svn/2.1.0.M2/gwt/maven/ > > > > > (I'm also using GWT 2.1.0.M2 from that repo) > > > > > > Oh, the 404 *is* due to the index.html not being in the war/ folder. > > > > > Running DevMode from the Eclipse plugin doesn't do anything Maven- > > > > > related, so it won't try copying files around. -- 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.
