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

Hudson commented on MJAVADOC-626:
---------------------------------

Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin » master #68

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/68/

> Detect stale files and skip generation if not needed
> ----------------------------------------------------
>
>                 Key: MJAVADOC-626
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-626
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>          Components: javadoc
>    Affects Versions: 3.1.1
>            Reporter: Guillaume Nodet
>            Assignee: Olivier Lamy
>            Priority: Major
>             Fix For: 3.2.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In Apache Camel, we do use javadoc during the build as we have a few things 
> that are generated from the javadoc.  However, javadoc can take quite some 
> time to build, so I came up with a stale file/config detection mechanism in 
> order to avoid recomputing the javadoc if there is no change.
>  
> The idea is to compute an _input_ _state_ consisting of all the command line 
> options (flattening the {{@xxx}} options) and the list of all input files 
> along with their last modification date.  Before actually executing the 
> command line, we compare the current state with the last saved state and skip 
> the execution if there is no change.
> The code is visible in this commit mainly: 
> [https://github.com/apache/camel/pull/3233/commits/57903a94f82413022afc594e374fb3dff4f7578a]
>  and if there is an agreement, I can create a correct PR to incorporate the 
> change.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to