[ 
http://jira.codehaus.org/browse/MJAVADOC-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240987#action_240987
 ] 

Benson Margulies commented on MJAVADOC-284:
-------------------------------------------

{code}
svn co https://svn.apache.org/repos/asf/mahout/trunk
maven 3.0 ...
mvn -Prelease
{code}



> detectOfflineLinks sets off extra spurious executions of javadoc
> ----------------------------------------------------------------
>
>                 Key: MJAVADOC-284
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-284
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6.1
>            Reporter: Benson Margulies
>
> I have an aggregate project. In pluginManagement, I spec out javadoc:jar. In 
> the leaf projects, I turn it on with an ordinary <plugin/> for the plugin.
> If I leave detectOfflineLinks with its default value of true, the javadoc 
> plugin uses the invoker plugin to relaunch itself, recursively, complaining 
> that it hasn't been run on one or another of the projects. Note that, when 
> this happens, it is 'swimming upstream' -- it is processing project A, it 
> invokes itself on project B, where B depends on A, not the other way around.
> If I run maven just in the leaf directories all is well. The trouble only 
> happens when running maven from the aggregating parent.
> Just to clarify, in case I don't get a test case together too soon ...
> external/corporate parent:
> javadoc only mentioned in the <reporting> section.
> aggregating parent:
> javadoc only mentioned in pluginManagement, setting up execution of 
> javadoc:jar.
> leaf:
> A very plain 'plugin' element just to turn on the configuration from plugin 
> management.
> mvn run from leaf: all is well.
> mvn run from aggregating parent: lots of extra 'invoker' invocations of 
> javadoc on projects that have dependencies on the current project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to