Generally, you should not be committing GWT's generated artifacts into
version control. Of course, this is completely up to you, but the usual way
to do this would be to tag your source code at a particular point and time,
and then use a build script to generate a war file for deployment.
As has
Ok thanks all, will do.
On Tue, Sep 29, 2009 at 10:04 AM, Rajeev Dayal rda...@google.com wrote:
Generally, you should not be committing GWT's generated artifacts into
version control. Of course, this is completely up to you, but the usual way
to do this would be to tag your source code at a
In our settings, we use Maven to build our project in our code
repository and push to the deployment server. We do not compile it
locally, thus we never commit those compiled files.
HTH
-Ben
On Sep 28, 2:54 pm, charlie charlie.f...@gmail.com wrote:
I'm having a hard time automating the build
If you have installed the toolkit there is an application that you can
call to generate shell / template projects for you. This will also
create a build file that you can take a look at. None of this has
anything to do with eclipse. If you have only used eclipse you might
need to download the
