> > What if we commit IDE configurations in the repository? (and make sure > they're updated each time we change the build; that would be similar to > today's situation, except that the IDE config could be generated from the > build scripts) >
Would be ok, although personally I wouldn't prefer it as IDEs tend to modify these files every now and then because of any kind of plugin in the IDE or whatever. I generally try to keep IDE configuration out of DVCS and let the IDE figure out how to configure itself based on the build file. What about Netbeans + Pants? > A new contributor could then work without a VM (for a small patch, running > tests in the IDE should be enough), until he wants/needs to use a custom > build of GWT in his projects; then he'd have to find a Linux or OS X > machine (or VM) to actually build GWT. > Would that be acceptable? > I would think so. As GWT now has SNAPSHOT builds a contributor could also use these after his patch has landed. The linux/unix requirement would then only hit people who apply custom patches on top of GWT or who don't use a dependency management tool that understands maven coordinates and prefer a SDK zip. Maybe we should publish such a snapshot SDK zip at gwtproject.org as well. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/8c902354-3f6d-439d-a89d-de3b11fc11bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
