When doing non-GUI projects, always go for cmd line! I personally hate IDE's. I use the command line to do any kind of project, whether it be GUI or not. I use the command line to compile, package, secure, etc all my programs. Can always be fully updated (latest JDK version = latest javac version). Don't have to worry about the tricks and hacks etc. When my programs were smaller than 300 lines, I used Microsoft's Notepad. I now use Notepad++, which ISN'T an IDE, just a syntax highlighter. I recommend this for you, Yatin Shah and everyone! Good luck on your path to
Java programming. Read the Java tutorials. Look up some online. Read some books (I recommend "Head First Java"). Then, go out and code. When you are having trouble or getting errors, try to look up the solutions online. Eventually, you'll learn (I learned this about a month ago) that you can figure out most of your problems by looking up the errors in the API. If you get an error, look up the error. Look at the attached component (NullPointerException from JTextField, look up NullPointerException if you don't know what that is. Then, look at the methods, constructors, etc that you used and find your problem). This is just some tips. Good luck!
cc11rocks
EDIT : For the exceptions, you'll usually find the problem line (within your actual code) in the first 1-2 lines of error message. Sometimes, there will only be
one line one line of error message with the line number and the other lines will be on an "unknown" line. This is obviously the problem line of code. Something I learned in the past week is to use generics with ALL of your collections (maps, lists, etc) if you can.