LifeCycleParticipant#afterProjectsRead is called after projects pom.xml
are read and MavenProject instances created but *before* actual build
starts. It is called for entire session and not any reactor project in
particular.
--
Regards,
Igor
On 2014-05-23, 21:03, William Ferguson wrote:
Thanks Igor.
A correct LifeCycleParticipant implementation should always scope
component lookups to the current project's classloader and should use
the original classloader to allow lookup of the core components only.
But in a multi-module build the LifeCycleParticipant is only ever called
once; for the top level project. So if the top level project does have have
the plugin configured then does that mean I have no ClassRealm to use?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
