[
https://issues.apache.org/jira/browse/LUCENE-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794068#comment-13794068
]
Uwe Schindler edited comment on LUCENE-5282 at 10/14/13 12:02 PM:
------------------------------------------------------------------
Hi, status update:
It is not as easy as expected. My idea how to fix the macro was to use the
similar approach like the javadocs-packages-file downloader. This was invoked
by "antcall", so if/unless properties were respected and updated. The idea I
had was the same: use {{<local>}} to define property, then {{<uptodate>}} on
the local property to find out if source files are newer than
{{@destdir/package.html}} (this is the recommended approach to detect javadocs
timestamp, see e.g. the official ANT build.xml), and finally execute the
javadocs task with {{<antcall>}}, passing the {{@}}-variables as parameters to
the task. The problem why this did not work is the {{<nested>}} sourcefiles
property, you cannot pass xml structures as parameters to a target. I found no
was around that.
The second problem: You cannot get the source folder with the Java files from
the macro: you only have the nested element that has the package names and
directories somewhere in them.
In my opinion the only was to fix this would be a separate uptodate task in
common-build and all module's javadocs targets depend on that one + ifunless
check.
was (Author: thetaphi):
Hi, status update:
It is not as easy as expected. My idea how to fix the macro was to use the
similar approach like the javadocs-packages-file downloader. This was invoked
by "antcall", so if/unless properties were respected and updated. The idea I
had was the same: use {{<local>}} to define property, then {{<uptodate>}} on
the local property to find out if source files are newer than
{{@destdir/package.html}} (see is the recommended approach to detect javadocs
timestamp, see e.g. the official ANT build.xml), and finally execute the
javadocs task with {{<antcall>}}, passing the {{@}}-variables as parameters to
the task. The problem why this did not work is the {{<nested>}} sourcefiles
property, you cannot pass xml structures as parameters to a target. I found no
was around that.
The second problem: You cannot get the source folder with the HTML files from
the macro: you only have the nested element that has the package names and
directories somewhere in them.
In my opinion the only was to fix this would be a separate uptodate task in
common-build and all module's javadocs targets depend on that one + ifunless
check.
> speed up javadocs generation tasks
> ----------------------------------
>
> Key: LUCENE-5282
> URL: https://issues.apache.org/jira/browse/LUCENE-5282
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
