Yeah, make sure to get the JDK as well as the JRE if you're going to be developing.
My little rant:
I used the FLTK library (which I had experience with from a class) to build a nice, small chess program. It wasn't great, but I'm proud of what I accomplished. I wanted to show it off to a friend of mine. So, I figured I would just compile FLTK for Windows, and use that DLL with an MSVC build of my program, since I had developed the program on Linux. FLTK is cross-platform, and my code had no platform-dependent pieces, so it should be easy, right?
Wrong.
After fighting plenty with Visual Studio (both 2010 and 2013 versions), I finally got FLTK compiled. So, I open up the chess project in VS, add the FLTK DLLs as references, and go to compile. Clean compile. I try to run the program, and I get told that I'm missing a MSVC DLL needed to run it. But wait, how can that be? I check my system32 folder, and there it is. I try copying it to the same folder as the executable. Nope, still doesn't work. Ffs, screw Visual Studio.
Ok, my options are Cygwin and MinGW. Cygwin works, but would basically require everyone who wants to run it to install Cygwin, as well as an X11 server. Not a viable option. So I fire up MSYS, and try to compile FLTK.
Oops, I'm missing cmake. Better install it. Oh, it's not in the MinGW Installation Manager's package list. Ok, install from source. Nothing new. Compiled, installed, and... MSYS can't find it. What the actual fuck. Screw with path a bit, try again. Ok, it found it, but it's complaining about missing some DLL. IT'S RIGHT THERE FUCKTARD. Try a native Windows cmake - it won't generate MinGW Makefiles without erroring out because of MinGW's Unix pathnames vs Windows pathnames.
Fuck it, I give up. I'll just develop it with MSVC directly, without FLTK. Which means rebuilding the GUI and the glue between the GUI and my original code.