If I remember correctly, you can set the instantiation policy for a Mojo. By default, it may be once which means it will never be released by Maven and kept as a singleton. May be you can have a look at this feature ?
Regards Jeff MAURY On Fri, Jan 22, 2010 at 3:50 PM, Laird Nelson <[email protected]> wrote: > Hello; I have created a more flexible version of the Maven OpenJPA plugin. > We use it to generate code from our massive 30-year-old database. > > It wraps an OpenJPA tool called the ReverseMappingTool. The > ReverseMappingTool generates all kinds of objects in memory as it runs. > > Our build dies midway through, because the ReverseMappingTool, run through > this plugin, never releases the objects it generates. At least I think > that's what I'm seeing. > > It appears that Maven never unloads plugins that it has configured, even > after any executions where they might be applicable have long since passed. > Is this true? Is there some sort of programmatic way to force Maven to > unload or null out a plugin after an execution? > > Thanks, > Laird > -- http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal
