I can echo the fact that learnign OO would be a very good first step.
You have used C++ in the past so have a good inkling of the basics of classes etc but C++ is (arguably) not truly OO. It was a concept "tacked" onto C++ when it became popular.
Java on the otherhand is entirely OO. I would suggest you master the concepts of packages, inheritance etc before you get to stuck into coding.
I made the mistake of not doing this, it meant that about 3 years in, although I could code, I was still learning the basics as and when I needed to know them ,as a result of this I was doing some vey silly things in my programs which could have been avoided or certainly done in a better way had my grasp on the fundamentals of OO been superior.
It really wont take too long. I also find using UML class diagrams is a very useful way of planning out a java app before I really get stuck in. Ok its not usually possible to draw up something 100% accurate before you have started but even just having an outline of the apps class structure can be very useful.
EDIT: Also i think this IDE vs command line stuff is a bit moot, come on the guy can program in C++ and is moving onto Java, ok he had a few teethign troubles but after a week or so messing round in an IDE, typing in "javac xxx" isnt going to really tax him(/her) too much. Personally I dont think it matters if people start in an IDE or not, its the coding itself that is important.
Oh, also, from the very start.... make use of the try/catch error handling structure, its one of Java's true strengths an again, my poor initial knowledge led me to not make use of it for far too long....