Its been a while admittedly since I dealt with a forked plugin, but yes I believe the executionProject is used when the lifecycle is forked. If you are interested in the forked roots, you would use that, otherwise fall back to the normal project.
On Thu, Oct 22, 2009 at 1:20 PM, Ryan Stewart <rds6...@gmail.com> wrote: > > I'm trying to modify a Maven plugin, and it currently uses > project.getExecutionProject().getCompileSourceRoots(). While trying > different configurations, I sometimes get a NPE because > getExecutionProject() returns null. I haven't been able to find a good > explanation of what this thing is. I gather that it has something to do with > forked lifecycles. Is the executionProject a new MavenProject that gets > created when you fork the build? When is it null and not null? If I need to > get the compileSourceRoots, should I first check the executionProject, then > fall back to the project if the former is null? > -- > View this message in context: > http://www.nabble.com/What-is-executionProject--tp26013909p26013909.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org