Community
Participate
Working Groups
Import from "existing maven project" triggers the search for lifecycle mapping, however it is not triggered when I import a project directly from the SCM, or when I create a new project using the archetype.
This is a subtask of bug 335701, I just did not want to mess with all wizards at once ;-) For archetypes, we'll likely have to execute project generation as part of the wizard... which is not exactly pretty GUI and requires relatively serious refactoring of project import manager... which I think is a good thing.
it starts taking an ugly turn. There was never mentioned that we want to do this ever (not to mention this iteration). And it's more or less proof that the original idea of having the stuff part of the wizards is wrong! Creating anything before the wizard finishes is a big no-no and I'm opposed to this change. We probably should get away without *any* wizard changes for this iteration/milestone and have the whole error recovery process re-thought from the ground
This is how import from scm wizards work already, they do checkout first, then do maven import after checkout has completed. But I agree with scheduling concerns, lets figure out import existing maven projects first, lets not worry about other wizards for now.
Lets keep this bug for import existing projects from scm and discuss issues regarding creating new projects from archetypes in Bug 339906.
I have a patch for this, it turned out to be fairly simple, I will push it after we tag for M6
http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=e23c45121cfaa93c678911b1115df71012e3e9bd
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
