This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
When I've had problems with Maven in Eclipse not acting like Maven from a command line, it's always been an Eclipse configuration issue. First, you want to be sure that Eclipse is using the correct version. Go into Window - Preferences, and choose Maven - Installations. If the embedded version of Maven isn't what you run from the command line, add the external Maven to the Installations and select it as the default. If that still doesn't work, look at Maven - User Settings, and make sure it's using the right path to your settings.xml and your repository.
Joined: Dec 09, 2006
I already had looked into these settings in Eclipse.
The error "resolution will not be reattempted until the update interval of central has elapsed or updates are forced" usually means that the local repository has some information about the JAR in question, but it might be partial or outdated information. Usually deleting the local repository, or in your case deleting the org/kitchen-eel directory, should clean up the situation. The other possibility is to run mvn with the -U option.
But it does sound as if Eclipse hasn't read the settings.xml file and is not looking at the correct location for the local repository.
Oh, did you change the Eclipse configuration to use your local copy of Maven, and not the one that comes with Eclipse?