[m2] optimizing custom plugin execution

[John Fallows <jo...@gmail.com>]

Folks,

I'm writing a maven2 plugin that needs to parse various xml metadata
files to drive it's behavior.

There are a number of different (optional) goals in the same m2 plugin
that need to consume the same xml metadata.

Right now, each different goal is a different Mojo, with different
instance state, so each Mojo is re-parsing the metadata files.

Is there a best practice for sharing information across goals within
the same plugin for the same lifecycle execution?

Could the metadata be parsed on demand, and then maybe stored
somewhere on the MavenProject for subsequent Mojos to locate?

Kind Regards,
John Fallows.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] optimizing custom plugin execution

[Brett Porter <br...@gmail.com>]

Not yet...

http://jira.codehaus.org/browse/MNG-823

- Brett

On 9/10/05, John Fallows <jo...@gmail.com> wrote:
> 
> Folks,
> 
> I'm writing a maven2 plugin that needs to parse various xml metadata
> files to drive it's behavior.
> 
> There are a number of different (optional) goals in the same m2 plugin
> that need to consume the same xml metadata.
> 
> Right now, each different goal is a different Mojo, with different
> instance state, so each Mojo is re-parsing the metadata files.
> 
> Is there a best practice for sharing information across goals within
> the same plugin for the same lifecycle execution?
> 
> Could the metadata be parsed on demand, and then maybe stored
> somewhere on the MavenProject for subsequent Mojos to locate?
> 
> Kind Regards,
> John Fallows.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
>