Re: [E] Re: Dynamically modifying MavenProject.getModel() so that sub-sequent lifecycle phases can pick up those changes

I know it's been over a year since I posted this question, but just wanted to say thanks. Using Maven plugin extensions to develop my plugin worked like a charm. I implemented com.exsoinn.maven.plugin.CodeQualityMavenLifecycleParticipant#afterProjectsRead hook to programmatically modify the Maven

Re: Dynamically modifying MavenProject.getModel() so that sub-sequent lifecycle phases can pick up those changes

On Mon 18 Dec 2017 at 18:10, Romain Manni-Bucau wrote: > Hi > > Did you try writing an extension instead of a mojo? It does exactly that (+ > few other things) > > Le 18 déc. 2017 19:03, "Quijada, Jose M" a > écrit : > > > I would like to write a

Re: Dynamically modifying MavenProject.getModel() so that sub-sequent lifecycle phases can pick up those changes

Hi Did you try writing an extension instead of a mojo? It does exactly that (+ few other things) Le 18 déc. 2017 19:03, "Quijada, Jose M" a écrit : > I would like to write a Maven plugin that among other things manipulates > (both add/update) the POM model available

Dynamically modifying MavenProject.getModel() so that sub-sequent lifecycle phases can pick up those changes

I would like to write a Maven plugin that among other things manipulates (both add/update) the POM model available at MavenProjects.getModel() while executing Maven phase goals, such as "test" and "site", so that for instance I can: 1) Add a node along with plugins inside, so that when the