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 environment variables). However, I can see justification in checking it in. Good luck! On Nov 21, 3:22 pm, jbdhl <[email protected]> wrote: > 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 located > differently for different developers. All scripts can just refer to > the same relative path(s). > Cons: > * It's kind of ugly to commit third-party stuff into the > project repository > > 2) Each developer download their own GWT version and let an > environment variable, GWT_ROOT, point to it. > Pros: > * No third party stuff in project repository > Const: > * Possible conflicts if developers use different GWT versions > * Possible problems with developers different placements of > GWT. > > What would you suggest? -- 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=.
