On Mon, Oct 20, 2014 at 11:47 AM, Thomas Broyer <[email protected]> wrote:
> > 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? > In my case it was the checkstyle plugin for eclipse that was not compatible with a newer eclipse version. But I gave up shortly afterwards. > > >> >> 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. > We always have some rogue developers who use vi or IntelliJ, but indeed we can be very enforcing on what developers have to use. On the other hand, requiring a VM for development is also a very heavy requirement. I've had to do such things on a Linux box (with windows in a virtual box) but that kept on breaking with every update of the linux kernel. But I am not an Linux expert. I stopped using it a very long time ago (95 or so) > 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 > Well one nice tool (from Google if I am not mistaken) is to use the workspace mechanic. We use that mostly to keep all our eclipse installations inline with our rules. Maybe that is an idea to make it easier. > 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). > I recently had to customize Bootstrap.css to be used in GWT (without GWT wrappers) and that was really a painful process. It was nearly impossible to get it working in the enterprise environment. I finally did it on my Mac at home. But I really hate the fact that nowadays everything seems to be using their own build systems. Sure ant is crappy and even maven is not great in many ways ... but boy I was surprised at how many newer things are available. Always new commands to learn, waste of memory cycles and confusion when switching between projects. Anyway, you guys asked for some feedback, there you have it from my point of view, feel free to do with it what you like :-) -- 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/CABrJHW0%2BV8i%3DC2_YK9kwK7bBd36vvziyjVmb2BnGB6nLNNoBxQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
