Brian E. Fox wrote:
Do you need @aggregator to make sure the reactorProjects is properly populated?
No, at least not just for inspection of the projects and their model.
Neglecting the run-once behavior of @aggregator, it would be required if
their dependencies needed to be resolved or lifec
Do you need @aggregator to make sure the reactorProjects is properly populated?
--Brian (mobile)
On Dec 20, 2010, at 12:18 PM, Benjamin Bentmann
wrote:
> Bernd Vogt wrote:
>
>> when implementing a Mojo (Maven 3), how do I get the MavenProject
>> objects of the modules that were already built
Looks like I had a rogue debugger process left around, the mockito
issue is still haunting me tho.
This is on a line doing:
doReturn(something).when(spiedObject).doSomething();
I'll create an example project and see if I can that to break.
--
"Great artists are extremely selfish and arrogant
> /** @parameter default-value="${reactorProjects}" */
> Collection projects;
That's exactly what I was looking for. Thanks!
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@mav
Bernd Vogt wrote:
when implementing a Mojo (Maven 3), how do I get the MavenProject
objects of the modules that were already built by the current reactor
build?
Sounds either like
/** @parameter default-value="${reactorProjects}" */
Collection projects;
or http://jira.codehaus.org/browse/MNG
Hi,
when implementing a Mojo (Maven 3), how do I get the MavenProject
objects of the modules that were already built by the current reactor
build?
Regards,
Bernd Vogt
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
