dchicks, With m2eclipse, steps you described can be folded nearly into one step. You may want to check it out. See, for example, how Maven Archetypes are integrated into the new project wizard. http://docs.codehaus.org/display/M2ECLIPSE/Creating+Maven+projects
You can say that Eclipse is not necessary, but it is certainly making working with Maven in the IDE easier. regards, Eugene dchicks wrote: > > After reading your first email, I think you have some ideas backwards. > Eclipse does not necessarily "control" what Maven does. Maven's > activities are all governed by the pom.xml file. To help simplify > things, why not take it one step at a time. > > First, create your Maven project. Use an archetype to generate the > starting point for yourself: > http://docs.codehaus.org/display/MAVENUSER/Archetypes+List > Next, build the project using Maven: mvn install (this will get all > your dependencies pulled into your local repository) > Next, create the necessary Eclipse project files from the Maven > pom.xml: mvn eclipse:eclipse > Now, when you open Eclipse, you can import the project and it will be > all happy with itself. > > Any time you need to add a dependency, it should be done through the > pom.xml. M2Eclipse (the Eclipse plugin) can help with this, but isn't > strictly necessary. > -- View this message in context: http://www.nabble.com/creating-a-maven-project-in-eclipse---very--new-bee-tp20135531p20140178.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
