[ http://jira.codehaus.org/browse/MNGECLIPSE-134?page=all ]
Eugene Kuleshov updated MNGECLIPSE-134:
---------------------------------------
Priority: Minor (was: Major)
Instead of your steps 2, 3 and 4 you can use Maven2->Update Source Folders
action. It suppose to do exactly that.
We have an open issu in regards to the target folder and as I suggested there
you can set your preferred defaults for project target folder in global Eclipse
properties.
Anyways, I am changing priority to minor. There is already stub for Maven
project in the code so if somebody would like to finish it we will be glad to
apply patch.
> 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
> Priority: Minor
>
>
> 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
