It looks like the javadoc plugin always fires up Velocity for some some
reason. The only work around I can see to the two questions below is to
use the usual antrun to run the ant javadoc task.
On 6/20/2007 10:05 AM, Paul Copeland wrote:
Any thoughts on what the "Removing: javadoc from forked lifecycle, to
prevent recursive invocation" means and why velolcity is run by the
javadoc plugin?
It seems like wanting to put javadoc in a webapp directory would be a
fairly common need - Should I use the antrun plugin instead?
On 6/19/2007 2:10 PM, Paul Copeland wrote:
I'm generating javadoc within a webapp context. I put the
maven-javadoc-plugin:javadoc goal into the package phase rather than
in the usual the generation <reporting> lifecycle. It is doing the
right thing but I get this message -
[WARNING] Removing: javadoc from forked lifecycle, to prevent
recursive invocation
Then I get a bunch of velocity messages (irrelevant for javadoc AFAIK)
Why do I get the message and can I get rid of velocity since this is
a plain vanilla javadoc tool run?
TIA - Paul Copeland, Jot Object Technologies http://www.jotobjects.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
