You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2017/05/10 13:51:04 UTC
[jira] [Commented] (JENA-1333) Make prepare-javadoc script take
version parameters and repo parameter
[ https://issues.apache.org/jira/browse/JENA-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004707#comment-16004707 ]
Andy Seaborne commented on JENA-1333:
-------------------------------------
Also needs the number of the nexus staging repo.
In defence of the current approach, it means the settings are recorded.
> 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)