Blog de Salvador Diaz

1. 
   Eugene Kuleshov
   May 1st, 2009 on 15h41

   You can change the default output folder used by Maven from target/classes to target/gwt/WEB-INF/classes in the pom.xml using build/outputDirectory element. In a form-based pom editor provided by m2eclipse it is the “Output” filed located on Build tab.
2. 
   nicolas de loof
   May 4th, 2009 on 8h37

   Just a note on the eclipse lauch configuration : it can be generated by the gwt-maven-plugin using “mvn gwt:eclipse”. This will also put all necessary libs in webapp WEB-ING/lib if not allready done.

   Your setup looks good but use the same webapp structure for hosted mode and target WAR. This may not be desirable if your server-side code is more than just few servelts : hosted mode is designed for quick and lightweigh devs, for real server testing use the -noserver option.
3. 
   Lakech
   May 4th, 2009 on 8h50

   Hi,

   I tried the exclusion to avoid the GWT issue 3439 with :

   javax/servlet/**

   But the javax class are in my war…

   I avoid this with a ant run delete but i would prefer to use the exclusion solution.

   Any idea ?
4. 
   Malte
   May 4th, 2009 on 10h02

   Thanks for this howto, but I found a fault in the gwt-maven-plugin configuration part. The runTarget parameter is missing and has to be set to Application/Application.html.

   Greetz
   Malte
5. 
   salvador
   May 4th, 2009 on 12h00

   @nicolas
   Generating the run target with gwt-maven-plugin would be the ideal solution, however I think there’s a bug that causes gwt:eclipse to generate an incorrect run target under certain circumstances. Is it solved yet ? As for the -notarget option, we have several large GWT projects and launching like I described in my post doesn’t feel sluggish or anything. Plus there are some downsides to running with the -noserver option that I’ll mention in my next post.

   @Lakech
   I haven’t yet been bitten by this particular bug (we haven’t migrated our GWT projects to 1.6 yet) so I can’t really answer right now. I’ll try to address this in my next post.

   
   @Malte
   the runTarget parameter is only needed for the goal gwt:run or gwt:debug. In this tutorial I don’t use those goals, instead I use the eclipse launcher, that’s why I didn’t configure the runTarget.
   I’ll talk about all of the goals available in gwt-maven-plugin in one of my next posts, so check back soon.
6. 
   KaffeineComa
   May 4th, 2009 on 18h15

   Merci bien, ça marche!
7. 
   limbicsystem
   May 4th, 2009 on 21h13

   Hmm, not working for me. It seems to not be creating any war directory (is it supposed to do that under target?) Why are you giving a “-war .” argument? Shouldn’t it be “-war target/SOMETHING” ?

   Anyway, thanks for taking this problem up.. it has been seriously neglected by Google, IMHO.
8. 
   salvador
   May 5th, 2009 on 8h01

   @KaffeineComa
   De rien ! Je suis content que ça marche.

   @limbicsystem
   The war directory under target is called gwt. If it’s not creating it, you might want to double check your m2eclipse settings (is “Skip maven compiler …” unchecked ?). As for the argument “-war .” : it is relative to the working directory so that translates to “-war target/gwt“
9. 
   limbicsystem
   May 5th, 2009 on 17h04

   It creates the target/gwt directory, it’s just that that directory seems to not be the “current” directory when the config is run. I have to use “-war target/gwt”, and then it works. Why is target/gwt the current-working-directory in your setup? I don’t see why that should be so.
10. 
    nicolas de loof
    May 6th, 2009 on 11h44

    The gwt:eclipse goal has no way to detect the startupUrl based on gwt modules in the webapp (or maybe you’ve got a suggestion ?). The generated launch configuration file are just a helper the user can edit to set it’s own config.

    I still have to check MGWT-29. Testcases and patches are welcome
11. 
    Dennis
    May 7th, 2009 on 13h14

    Thank you for this great tutorial!

    I do though have one newbish question. When I run the debug configuration I get the following error:

    [ERROR] Unable to find ‘Application/html.gwt.xml’ on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?

    If I change the -startupURL Application.html to -startupURL Application it seems the filename is correct but it still does not compile.

    What am I doing wrong?
12. 
    salvador
    May 7th, 2009 on 17h54

    @Dennis
    That’s a tough question to answer without further details. Fortunately for you I helped somebody who was having the same problem this morning and it turns out that his -war parameter was wrong. Make sure you didn’t forget the dot after it. It must read -war .
13. 
    javapda
    May 8th, 2009 on 22h51

    Thank you for the great post!

    I have been able to run the application and debug using maven.

    Does this build the test objects?
    When I rename GwtTestSample to GwtTestSampleTest and then run a mvn test there are failures in that it cannot find the compiled test classes.

    Thanks again
14. 
    Dennis
    May 9th, 2009 on 10h58

    Thank you so much! That was exactly the problem.
15. 
    Anthony
    May 11th, 2009 on 14h29

    Hello,

    Thank your for this tutorial.

    I had the same problem than Dennis and your response helped me to correct it.
    Meanwhile, I have nom a new similar error when I run the debug configuration :
    [ERROR] Unable to find ‘fr/salvadoriaz/gwt/sample/Application.gwt.xml’ on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?

    Can you help me ?

    Thanks.
16. 
    Anthony
    May 11th, 2009 on 16h04

    Sorry for my precedent post !!
    I think I have made a mistake in my debug configuration.
    It’s working now.

    Thanks a lot
17. 
    Petit
    May 14th, 2009 on 11h07

    Hi,

    I think you should note on your tutorial that you should use “-war .” on the launcher configuration and emphasis on the dot.
    I just lost 2h figuring out that this tiny little dot was not a dead pixel or a dust on my Hd screen.

    Thanks for the tutorial.

    Chris
18. 
    limbicsystem
    May 27th, 2009 on 18h50

    I had this setup happily working for a week or so, then yesterday it mysteriously started failing about 75% of the time on our build server. It turns out that the gwt-maven-plugin does not always respect the config param. This was maddening, because it seems to work some of the time, depending on what happens to be in your plugins cache (and perhaps the phase of the moon.)

    We have it working reliable now after changing this to , as documented in the plugin web site:
    http://mojo.codehaus.org/gwt-maven-plugin/1.1-SNAPSHOT/compile-mojo.html
19. 
    Jay Kang
    May 29th, 2009 on 5h50

    Great article!! I’m not using GWT 1.6.4 at the moment, but really appreciated the in depth description of the setup process. <3 pictures. I’m awaiting for your next post, hope it’s on multi-project layout!
20. 
    matt
    May 29th, 2009 on 22h42

    Does anybody have a clue how to include other artifacts where classes and source are in separate JARs? m2eclipse doesn’t seem to honor the sources attribute when updating the project configuration. Thanks!
21. 
    rl
    June 9th, 2009 on 17h13

    Thanks for the useful article. I am having trouble when I do a mvn clean package. I am getting the following error and I’m not sure where the problem is.

    It seems like /target/gwt/myapp IS NOT created but /target/test-project-1.0-SNAPSHOT/myapp IS created. As a result, when Maven tries to copy it fails with this error:

    [INFO] [resources:testResources]
    [INFO] Using ‘UTF-8′ encoding to copy filtered resources.
    [INFO] skip non existing resourceDirectory c:\src\test-project\src\test\resources
    [INFO] [compiler:testCompile]
    [INFO] Nothing to compile - all classes are up to date
    [INFO] [surefire:test]
    [INFO] No tests to run.
    [INFO] [war:war]
    [INFO] Packaging webapp
    [INFO] Assembling webapp[test-project] in [c:\src\test-project\target\test-project-1.0-SNAPSHOT]
    [INFO] Processing war project
    [INFO] Copying webapp webResources[c:\src\test-project/target/gwt/myapp] to[c:\src\test-project\target\test-project-1.0-SNAPSHOT]
    [INFO] ————————————————————————
    [ERROR] FATAL ERROR
    [INFO] ————————————————————————
    [INFO] basedir c:\src\test-project\target\gwt\myapp does not exist
    [INFO] ————————————————————————
    [INFO] Trace
    java.lang.IllegalStateException: basedir c:\src\test-project\target\gwt\myapp does not exist
    at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)

    What should I look at? I reviewed the pom.xml here against mine and the Eclipse screenshots but haven’t pinpointed the issue.
22. 
    rl
    June 9th, 2009 on 18h33

    BTW - Looks like this blog stripped out the XML tags in my comment above.

    I believe this article uses the configuration parameters for the OLD gwt-maven-plugin from Google code BUT uses the NEW plugin from Codehaus. Can someone elaborate on this discrepancy? Seems like the pom should use the NEW parameters.

    OLD:

    http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/compile-mojo.html

    (has “output” has a config parameter)
    output

    Location on filesystem where GWT will write output files (-out option to GWTCompiler).

    * Type: java.io.File
    * Required: No
    * Expression: ${project.build.directory}/${project.build.finalName}

    NEW:
    http://mojo.codehaus.org/gwt-maven-plugin/1.1-SNAPSHOT/compile-mojo.html

    webappDirectory:
    Location on filesystem where GWT will write output files (-out option to GWTCompiler).

    * Type: java.io.File
    * Required: No
    * Expression: ${gwt.war}
    * Default: ${project.build.directory}/${project.build.finalName}

    AND has a REQUIRED parameter:

    generateDirectory:
    Folder where generated-source will be created (automatically added to compile classpath).

    * Type: java.io.File
    * Required: Yes
    * Default: ${project.build.directory}/generated-sources/gwt
23. 
    salvador
    June 12th, 2009 on 12h18

    Well, since the SNAPSHOT version is a moving target I’m not sure it hasn’t changed since I wrote this tutorial. I’ll be sure to check it and update the article.
24. 
    mariusz.pala
    June 15th, 2009 on 16h33

    I agree, “output” tag should be replaced with “webappDirectory”, otherwise package doesn’t work.
    Also to avoid stack overflow exception you can add
    extraJvmArgs tag: -Xmx512m -Xss1024k
25. 
    Jason
    June 17th, 2009 on 17h36

    @rl i ran into the same problem, i thought i was doing something wrong. salvador is there a fix for this?

    this tutorial has been a great help!

    jason
26. 
    Aaron Digulla
    June 18th, 2009 on 15h18

    @rl: The fatal error is because of the webResources path in the maven-war-plugin. Replace

    ${gwt.output.directory}/${gwt.module.alias}

    with

    ${basedir}/target/${project.name}-${project.version}/${gwt.module.alias}

    and the error goes away.

    As to the rest of the article, here are my comments:

    #1: Don’t *ever* add “compile” to the Maven Project-level configuration. Never. Never. Ever! This will seriously confuse the Eclipse IDE and you’ll suddenly get errors that classes can’t be found which are obviously there (F3/”Open Declaration” can find them, but the Java compiler can’t).

    #2: Change the order of the GWT dependencies. Make sure that “gwt-user” comes first. This way, you will have the GWT sources for debugging. Note that this only works with the latest version m2eclipse which honors the order of the dependencies in the pom.xml.

    As I said above, the latest version of the gwt-maven-plugin seems to have changed the paths where it will write the results of the compile step.

    #3 If GWT hostes mode complains that it can’t find the sources, open the “Run Configuration”, select your launch config, open the tab “Classpath” and make sure that the source folders are correct.

    For some reason, Eclipse 3.5 won’t let you edit this field. You have to open the launch XML file and fix the path manually. Look for a “internalArchive”.

    #4 Some comments about Eclipse 3.5: Yes, it works with the latest m2eclipse. You can’t use the GWT plugin, yet, but you can import a project created with the command line tools of GWT 1.6, enabling Maven2 and then making all the changes outlined here.
27. 
    rl
    June 24th, 2009 on 19h52

    Salvador - Can you update the pom.xml in this article to work with the 1.1 release of the plug in and incorporate the changes discussed in the comments. That would be a big help! thanks! merci!
28. 
    rl
    June 24th, 2009 on 20h48

    Aaron,

    I’m not sure what to after reading your statement:

    “#1: Don’t *ever* add “compile” to the Maven Project-level configuration. Never. Never. Ever! This will seriously confuse the Eclipse IDE and you’ll suddenly get errors that classes can’t be found which are obviously there (F3/”Open Declaration” can find them, but the Java compiler can’t).”

    I have the following code defined for the plugin:

    http://pastebin.ca/1473104

    What changes do I need to make?
29. 
    rl
    June 29th, 2009 on 15h52

    Can someone post an up-to-date working pom.xml? The one in this article has issues.

    BTW - I noticed that several comments are missing from this blog. Was there a server crash?
30. 
    gamUssA
    July 1st, 2009 on 11h00

    @rl
    pom.xml which works fine for me http://dumpz.org/10234/
31. 
    gAmUssA
    July 1st, 2009 on 11h06

    @rl
    pom.xml which works fine for me http://dumpz.org/10234/

    for Eclipse 3.5 works fine too.
32. 
    Pepe
    July 5th, 2009 on 15h01

    Is it just me or does the gwt-maven-plugin documentation really suck compare to gwt-maven plugin hosted at Google?
33. 
    Diogo
    July 20th, 2009 on 20h08

    Great post Salvador, it’s very helpful…

    Thanks.
34. 
    Dennis
    July 21st, 2009 on 14h42

    Is it possible to somehow not create the Eclipse project configuration manually e.g have it created automatically in the POM for instance? It would be great for when other people in my team checkout the project e.g. so they could just checkout the project from SVN and it would run “out of the box”.

    PS. Thanks for the great tutorial!
35. 
    picosam
    August 27th, 2009 on 22h01

    Thank you, I confirm that this works with GWT 1.7 and Eclipse 3.5; will keep you posted if there are any “breaks”, and I would love to hear about any improvements that you would achieve!

    Merci, je confirme que cela marche avec GWT 1.7 et Eclipse 3.5; je vous tiens au courant s’il y a des irrégularités, et j’aimerais savoir si vous faisiez des avancement sur le sujet !
36. 
    baguee
    September 29th, 2009 on 20h51

    Great job! Thanks a lot! (GWT 1.7, Eclipse 3.5)
37. 
    Judge
    October 11th, 2009 on 11h06

    The problem ocurred when I wanted to add spring security to my app. Here’s the problem: Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http://www.springframework.org/schema/security]
    Offending resource: class path resource [applicationContext-security.xml]

    Any ideas?
38. 
    Ram
    October 21st, 2009 on 11h28

    the links to the images are dead
    http://bayimg.com/image/japaoaabg.jpg
39. 
    ram
    October 22nd, 2009 on 9h34

    Great tutorial. Good work salvador, but the images are missing.
40. 
    mohammad riaz
    October 22nd, 2009 on 16h13

    This is a good tutorial for gwt and maven integration.
    I see the configuration images for “Main” tab, the “Arguments” tab, the “Classpath” tab are not loaded.

    Salvador, can you please zip the images so that we can download the zip.
41. 
    mohammad riaz
    October 23rd, 2009 on 17h31

    Thanks Salvador. You are real quick in helping.
    Now the downloadable zip consists the screenshots
    of the dead image links.
42. 
    Jon
    October 30th, 2009 on 23h16

    I am trying to execute this step by step, and cannot get past the command line step to create the project. I think something has changed since this was posted:

    “BUILD FAILURE”
    “The desired archetype does not exist (org.apache.maven.archetypes:gwt-maven-plugn:1.1-SNAPSHOT)”
43. 
    salvador
    November 15th, 2009 on 13h10

    @Jon:

    I don’t know if it changed, I haven’t had time to fully update the tutorial since I wrote it, and for that I’m really sorry.

    That being said, you might want to check the plugin usage instructions, and specifically the archetype generation instructions.

    Hope that helps !

Laisser un commentaire

• Posts récents

  • Keep your source tree clean ! Maven workarounds for GWT 1.6

• Tags

  eclipse english GEP GWT m2eclipse maven

• Catégories

  • GWT
  • maven

• Meta

  • Log in
  • Valid XHTML