On Sunday, October 19, 2014 8:28:45 PM UTC+2, stuckagain wrote: > > Sounds like a hasle to require a VM... unless that VM would include > everything to get started. > > Just setting up eclipse to be inline with the coding guidelines in GWT and > setting up all the libraries etc are really painful >
This is what the move to another build tool is also supposed to make easier (but it's not the main goal, at least not from my point of view); to begin with by having IDE configurations generated from the build scripts (and/or using Gradle integration in IDEs) rather than maintained in parallel (and generally forgotten, so they become out-of-date). I'm also looking for a build tool that can download external dependencies so you don't have to "svn checkout" the gwt-tools; but we need to be able to download from gwt-tools, at least for a transition period (and guess what: Gradle can't do that actually) and you need to follow the steps very carefully (and hopefully no > dependency has been changed since the document was written). > I'm curious, which dependencies are you talking about? > > What we do (in an enterprise environment) is to just have a zip or machine > image ready to be installed on a new machine. After 30 minutes or so a new > developer is ready to code. > In an "Enterprise" environment, you want to "control" the development environment so you don't give many choices to the developers. Here, we want to support different IDEs, we don't want to force you to use Eclipse or IntelliJ IDEA or whatever other IDE. Maintaining those ZIPs or images is also going to be a hassle I believe. I would like to have scripts to help setup the environment, and maybe we could have a script that downloads and configure Eclipse for instance (I doubt it though); we should have a script to setup the Gerrit commit-msg hook without the need for the contributor to think about it (just run "setup.sh" or "setup.bat" and it does the right thing; I fear it wouldn't be that easy on Windows though; on Linux, where every tool is an apt-get or yum call away, things are much easier, not to mention that distributions come with many tools pre-installed: I think every distro comes with Python pre-installed because it's needed by other tools already, it might also be the case on OS X; but everything seems complicated on Windows, with installers that you need to go look for, download, run, answer the questions –i.e. click "next" and "OK"– then reboot the machine if you're unlucky; n ow maybe I'm overly pessimistic and the needed tools come bundled with "Git for Windows", but I know some people won't even install that and instead use the JGit integrated within their IDE – and that won't work for us because IIRC JGit doesn't run git hooks). Imagine that I could just ask you to have Vagrant installed on your machine; the steps to contribute would be "git clone" and "vagrant up" (we could even do the "git clone" from within the VM, but I'm not sure it's worth it; the VM would setup the commit-msg hook though), then you can "vagrant ssh" into the VM to launch any build tool that GWT uses, and use "vagrant halt" or even "vagrant destroy" when you're done. As for the IDE, launch a command to generate IDE configuration files (depending on your IDE) that you can open (and when the project changes, just run the command again and refresh the project in your IDE to get the modifications); I'm not talking about running the IDE within the VM, we want you to keep with your habits and use the IDE you like, the way you like it; you should only have to configure the code style, and for that I believe we could provide files that you can just import (this is already the case for Eclipse). On Linux or OS X (or BSD, etc.), you could run scripts directly on your machine so wouldn't even need Vagrant, unless you want to keep your machine clean. Note: this is all speculative at this point! I was just taking the temperature. -- 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/e97238a2-f063-4a0d-9317-50a4fc25420c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
