On Tue, Aug 23, 2011 at 6:14 PM, Hervé BOUTEMY wrote:
> no
>
> IMHO, javadoc plugin documents both reporting and build tags [1]
It's the aggregate IT in javadoc that sent me off the rails. I'm better now.
>
> but only reporting should be used
>
> and it works perfectly for Maven core 3.0.4-SNAPS
no
IMHO, javadoc plugin documents both reporting and build tags [1]
but only reporting should be used
and it works perfectly for Maven core 3.0.4-SNAPSHOT: really, jxr aggregate
support is fine actually when configured as reporting
and we should promote reporting configuration only
Regards,
On Tue, Aug 23, 2011 at 5:26 PM, Hervé BOUTEMY wrote:
> I have been confused for a long time too, but finally had some explanations I
> can try to summary here: not sure it will give every answers, but at least I
> suppose it will help.
Hervé,
So far so good, and you can see that I cribbed an ex
I have been confused for a long time too, but finally had some explanations I
can try to summary here: not sure it will give every answers, but at least I
suppose it will help.
It has to do with the difference in API between a maven plugin (execute method
from plugin-api [1]) and a reporting pl
I am somewhat confused by the design of the site plugin with respect
to adding additional goals.
The new pattern is to move from 'aggregate' configuration property
booleans to more goals. However, goals have to be called out in
executions, and the reporting section can't spec an execution, and
we'
This is embarassing. There must be some simple mistake here, but I
wonder if any of the other JXR hackers could offer me a clue before I
start blundering around?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For addit
