[
https://issues.apache.org/jira/browse/JENA-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004716#comment-16004716
]
A. Soroka commented on JENA-1333:
---------------------------------
That's a good point. I wonder if we can record that as metadata somewhere
instead, perhaps in the docs themselves... nothing about that seems like
privileged info.
> Make prepare-javadoc script take version parameters and repo parameter
> ----------------------------------------------------------------------
>
> Key: JENA-1333
> URL: https://issues.apache.org/jira/browse/JENA-1333
> Project: Apache Jena
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: Jena 3.3.0
> Reporter: A. Soroka
> Assignee: A. Soroka
> Priority: Trivial
> Fix For: Jena 3.4.0
>
>
> Currently the prepare-javadoc script we use from dist-tools to generate
> Javadocs for a release has the versions of the release and the decision as to
> whether to use a local or released set of jars hard-coded. We should
> parameterize that for convenience and clarity.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
