While Maven is the way to go in the long term, the best way to start a project in Eclipse is:
- Hit Ctrl+N and choose Java project
- Fill in the project name fields
- Copy your files from wherever they are to the newly created project (ensuring to preserve package hierarchy)
- Refresh project from File menu
- Create a Run / Debug profile to run your app.
It should be fairly simple to get up and running this way.
The reason people recommend Maven is because Eclipse is an IDE. It's great for development but its no good for resolving external dependencies or for command line / automated builds. Maven is an IDE neutral way of building and becomes essential the more dependencies a project pulls in.
Unfortunately Eclipse integration with Maven is pretty clumsy and can be summarized with these very broad steps:
- Install Eclipse Helios
- Install m2eclipse from the Help | Eclipse Marketplace
- Mess around with eclipse.ini to make Eclipse start from a JDK.
- Configure m2eclipse to use any existing Maven local repository
- Hit Ctrl+N and create a new Maven project and skip archetype selection
- Copy all the source files from the old project into the new ensuring to use Maven's conventions for file locations. (e.g. source goes in src/main/java)
- Create a Run / Debug maven target to clean / install the app
I say broad steps because there are a lot of gotchas. For example if the source is Java 5+ you might have to tweak the pom to set the compiler level. Best to get Eclipse working and then worry about Maven.
Netbeans has vastly better out of the box support for Maven although IMO Eclipse is still the better IDE for other reasons.