Re: Large Project Structure

You can think about Maven as building toolkit for your project.

It's allow you to make a hierarchical and linear dependencies between modules

which decrease project total complexity.

More details you can find here: http://maven.apache.org and here: http://mojo.codehaus.org/gwt-maven-plugin/

This article also could be informative for you: http://code.google.com/p/gwt-maven/wiki/BigProjectBestPractices

On Tue, May 29, 2012 at 3:26 PM, Niraj Salot <salotniraj@gmail.com> wrote:

Hi All,

What should be consider as Best Practice for Large Project Structure ?

We have multiple modules inside the projects. Also We would like to
make sure that single change in one module does not require compile of
all the files. It should be just that module only.

How to achieve this in GWT Project Structure ?

Regards,Niraj Salot/

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

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