Thank you so much for your always invaluable feedback.

I am investigating your suggestions at the moment.

following your comment:
"splitting client/shared/server into 3 distinct modules, with a 4th one to 
pull client and server together into a webapp (client and server both 
depending on shared)."

so far I have created the structure below,

- do you think the settings below, is correct ? (considering our app is 
named 'expense')

*expense-app:* packaging pom, modules: expense-client, expense-server, 
expense-shared, expense-webapp

*expense-client:* packaging jar - parent: expense-app, dependency: 
expense-shared  - structure: src/main/java

*expense-server:* packaging jar - parent: expense-app, dependency: 
expense-shared - structure: src/main/java

*expense-shared:* packaging jar - parent: expense-app - structure: 
src/main/java

*expense-webapp:* packaging war - parent: expense-app, dependency: 
expense-client, dependency: expense-server - *structure: src/main/webapp*

[please refer to links below]
- the way directories are structured in filesystem, expense-app is the top 
level directory with 4 sub-directories:
expense-client,expense-server,expense-shared,expense-webapp (these 4 are 
siblings)

however when I type mvn clean install, in my local repository, I see 5 
distinct directories at the same level, 
in other words, expense-client, expense-server, expense-shared, 
expense-webapp, and expense-app,
are all at the same level, and client,server,shared,webapp are not inside 
the expense-app directory.
is this correct ?

- structure as they sit in file system
http://oi52.tinypic.com/10h3ipy.jpg

- structure in local repository after mvn clean install
http://oi51.tinypic.com/33e7yxl.jpg

Thank You

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

Reply via email to