Re: 3-tier architecture /gwt

Hi Thomas,

I try to install the archetype but said that:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] gwt-maven-archetypes .............................. SUCCESS [0.344s]
[INFO] modular-webapp .................................... FAILURE [4.469s]
[INFO] modular-requestfactory ............................ SKIPPED
[INFO] guice-rf-activities ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.172s
[INFO] Finished at: Thu May 31 21:33:24 GFT 2012
[INFO] Final Memory: 7M/17M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2
.2:integration-test (default-integration-test) on project modular-webapp:
[ERROR] Archetype IT 'basic-webapp' failed: Some content are not equals
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command

[ERROR]   mvn <goals> -rf :modular-webapp


Whatt's the problem?

2012/5/3 Thomas Broyer <t.broyer@gmail.com>

On Thursday, May 3, 2012 4:25:58 PM UTC+2, Joseph Lust wrote:

This topic has been discussed on SO and other places.

I am familiar with the suggested GWT archatype, but we found it limiting for large projects. Instead, we (40 devs) use the following Maven project structure to break up our project:

• MainProject.pom
• Client-Interfaces.pom (or POJO's as you put it)
• Client-GWT.pom (frontend GWT code, uses Interfaces)
• Server.pom (backend Java code, uses Client-Interfaces)
• Web.pom (Tomcat settings)

So just running the main pom will build the interfaces that are then used by the server side code and the client side GWT. The Web project contains Tomcat specific items and dictates how the war is packed up.

Benefits: You don't need to rebuild the whole project if changes are only in your services. Great because services compile in a few seconds, GWT in several minutes.

Just a quick note: this is exactly what https://github.com/tbroyer/gwt-maven-archetypes does (except for the server vs. web separation; that's something we did in our project too, but I didn't think it was worth putting into the archetypes: people should just split the module if/when they feel the need for it; I might add it to another archetype though); this is not the same as the archetype from the gwt-maven-plugin!

Announcement: http://tbroyer.posterous.com/announcing-gwt-maven-archetypes-project

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/r-lqZNBrjWUJ.

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.

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