Brian Fox wrote:
What is the behavior in an embedded env like M2e? Since it's not going to execute the full lifecycle, it probably needs to have the same logic regardless to look at the lifecycle and pick the right version of a plugin it does run.
Not sure I understand that question. Embedders of M3 would use M3 APIs and components so whatever we realize in M3 core will be available for the embedder as well.
For instance, the lifecycle mappings get merged into the effective POM. So whatever uses the ProjectBuilder and asks it to process plugins will get a model that reflects inheritance, plugin management and lifecycle mappings. Hand the resulting MavenProject to the lifecycle executor and you get back the execution plan, with all plugin versions resolved.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
