Making them stumble through an inconsistent, clumsy interface to do a simple thing like adding a .jar to the classpath is not its job.
Then encourage an IDE with a better interface. There's plenty to choose from.
OK, my fault if I didn't come accross correctly, but the point I am trying to make is that you can't always rely on IDEs to be there, like in servers that can only be accessed via terminal.
If you're doing serious development, you can always rely in IDEs to be there. Yes, there are times when it's useful to SSH into a server and do stuff programmatically, but that's what scripting languages like Perl are for. C++ and the like are for times when you want to build an actual application.
If you want to make some quick changes, it can be very helpful to be familiar with a command line editor.
There's no such thing as a "quick change" in real development. Common workflow steps include checking in and out of source control and running smoke/regression tests, even for the simplest code changes.
Even if you don't have any real infrastructure, the scenario you are describing is one of editing an existing program. It isn't applicable to learning how to create a new one.
---
http://thecrankyhermit.wikispaces.com/
Year-by-year analysis of the finest gaming has to offer, and (eventually) more!