I recommend you put it in your VCS. Having it in the repository does not
impact anyone negatively and makes everybody's life easier. If you must,
set up your project so that you can override the default version by
changing a per-developer setting or an environment variable and you're
good to
I can't decide where we should place GWT itself for a project with
multiple developers:
1) In the svn repository as part of the project.
Pros:
* The developers GWT version will always match what is being
used in the project
* No potential problems with GWT binaries being
You list good pros and cons so you'll have to just decide which is the
stronger argument for your situation.
Since our project is developed in mixed environments, and the
developer base isn't very big, it made sense for us to go with your
second option (although we use property files not
I think in an ideal dream the Project Manager would be able to create a work
breakdown structure that would reflect granular components that could be
checked out by the appropriate party(ies). This would make it easy to report
status of progress if executed properly. Make the project architecture
