[ 
https://issues.apache.org/jira/browse/MJAVADOC-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798126#comment-16798126
 ] 

Jonathan Coustick commented on MJAVADOC-587:
--------------------------------------------

Attached error log. The package it cannot find is not there as the pom for the 
libpam module has the clean plugin configured in the build section, and this is 
triggered by the Javadoc plugin (which it shouldn't) resulting in the jars in 
the target directory of libpam not being there when it is needed by building 
the javadoc of the security-ee module.

> Running plugin causes other phases to be executed
> -------------------------------------------------
>
>                 Key: MJAVADOC-587
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-587
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.1, 3.1.0
>            Reporter: Jonathan Coustick
>            Priority: Major
>         Attachments: error.log
>
>
> When running the javadoc plugin (either through javadoc:aggregate or via 
> profiles) it kicks off maven and all other plugins that are configured to run 
> via the <build> section of the pom are also started, which ends up causing 
> errors as they have their own expectations about the state of the project. 
> This only occurs in since version 3.0, earlier versions of this plugin do not 
> cause issues.
>  
> Reproducible with [https://github.com/payara/Payara/] with mvn 
> javadoc:aggregate -Ddoclint:none



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to