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

ASF GitHub Bot commented on MJAVADOC-444:
-----------------------------------------

DiJu519 commented on issue #2: [MJAVADOC-444] add aggregate-no-fork and 
aggregate-test-no-fork for non-forking versions of aggregate goals.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/2#issuecomment-404299254
 
 
   @khmarbaise @busbey 
   
   I just rebased this change locally to master it and it built successfully. 
   
   mvn clean verify failed the first time, similar to the error you posted 
@khmarbaise , but a second rebuild went through fine. 
   
   I think there's something behind the scenes with artifact resolution issues 
going on. I've seen this non-deterministic behavior lately while using mvn.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add an 'aggregated-no-fork' goal
> --------------------------------
>
>                 Key: MJAVADOC-444
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-444
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.10.3
>            Reporter: Karl Heinz Marbaise
>            Priority: Critical
>
> Currently you can call maven-javadoc-plugin via {{mvn clean package 
> javadoc:aggregate}} which results in deleting all previously created 
> artifacts in {{target}} folder. So it would be helpful having a separate goal 
> without forking the life cycle.



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

Reply via email to