speed up javadocs generation tasks [LUCENE-5282]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
These generate the same things over and over. I think this is due to javadocs always rebuilding their dependencies.
Can we not add a fake timestamp file (with 'touch') somewhere like javadocs.generated and then use 'uptodate' comparing that against the relevant source code to determine if javadocs need regeneration?
This seems like it would be a very simple solution.
---
Migrated from [LUCENE-5282](https://issues.apache.org/jira/browse/LUCENE-5282) by Robert Muir (@rmuir), updated Oct 14 2013
Contributor guide
Research direction
Start by locating the javadocs generation tasks and their dependency or up-to-date configuration. Check how relevant source changes are detected and how generated output is marked; done means unchanged sources skip regeneration while changed sources still trigger it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100