[ http://jira.codehaus.org/browse/MNGECLIPSE-134?page=comments#action_66980 ]
Scott Cytacki commented on MNGECLIPSE-134: ------------------------------------------ Here are the steps I have to do when checking out a simple maven project: - give it a name: there is no default name suggested by the New Java Project wizard - specify the jre - set the src/main/java and src/test/java folders as source folders - change the output folder: I prefer to separate it from target/classes so the too compilers don't collide - use Maven2->Enable Maven I think those steps are worth a wizard. Really they are just setting up the defaults for the new java project wizard. Hopefully it is easy to set those defaults. > wizard for creating java project from existing pom.xml > ------------------------------------------------------ > > Key: MNGECLIPSE-134 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-134 > Project: Maven 2.x Extension for Eclipse > Type: New Feature > Components: Wizards > Reporter: Scott Cytacki > Assignee: Eugene Kuleshov > > > When checking out a maven project from an scm that doesn't include .project > .classpath files. It would be nice if the maven plugin gave the option to > create the eclipse java project as it is being checked out. This is appears > to be handled by making a new project wizard. > An example of similar functionality is when checking out a ant based project > you can create an eclipse project from it. > The current solution is to check it out and then fix it up after the fact, by > adding the maven library, or instead runing the eclipse:eclipse goal. > The wizard could detect things like multimodule projects and at least give > some advice to the user, or better it might beable to give the user different > options for handling them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
