[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[
https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472756#comment-16472756
]
Hoss Man commented on SOLR-10616:
-
{quote}The parameters are all in the {{_config.yml.template}} file.
{quote}
NOTE: they also have to be put in the corrisponding section of build.xml so
they work in the PDF build (eventually i'd like to write our own ant
task/hook/launcher so we can just keep them all in one place, and verify that
they aren't blank/unset – which is currently a risk if someone changes the
variable names in the ivy-versions.properties file)
> use more ant variables in ref guide pages: particular for javadoc &
> third-party lib versions
>
>
> Key: SOLR-10616
> URL: https://issues.apache.org/jira/browse/SOLR-10616
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
>Reporter: Hoss Man
>Assignee: Hoss Man
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-10616.patch
>
>
> we already use ant variables for the lucene/solr version when building
> lucene/solr javadoc links, but it would be nice if we could slurp in the JDK
> javadoc URLs for the current java version & the versions.properties values
> for all third-party deps as well, so that links to things like the zookeeper
> guide, or the tika guide, or the javadocs for DateInstance would always be
> "current"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[
https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472647#comment-16472647
]
Cassandra Targett commented on SOLR-10616:
--
Yes, all you need to do is put {{\{ivy-zookeeper-version}}} where you want the
ZK version # to be inserted, including in URLs, like this example from the ZK
ACLs page:
{code}
This section describes using ZooKeeper access control lists (ACLs) with Solr.
For information about ZooKeeper ACLs, see the ZooKeeper documentation at
http://zookeeper.apache.org/doc/r{ivy-zookeeper-version}/zookeeperProgrammers.html#sc_ZooKeeperAccessControl.
{code}
Javadocs are done similarly (from the same page):
{code}
Solr nodes, clients and tools (e.g., ZkCLI) always use a java class called
{solr-javadocs}/solr-solrj/org/apache/solr/common/cloud/SolrZkClient.html[`SolrZkClient`]
{code}
The parameters are all in the {{_config.yml.template}} file.
> use more ant variables in ref guide pages: particular for javadoc &
> third-party lib versions
>
>
> Key: SOLR-10616
> URL: https://issues.apache.org/jira/browse/SOLR-10616
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
>Reporter: Hoss Man
>Assignee: Hoss Man
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-10616.patch
>
>
> we already use ant variables for the lucene/solr version when building
> lucene/solr javadoc links, but it would be nice if we could slurp in the JDK
> javadoc URLs for the current java version & the versions.properties values
> for all third-party deps as well, so that links to things like the zookeeper
> guide, or the tika guide, or the javadocs for DateInstance would always be
> "current"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472616#comment-16472616 ] Mark Miller commented on SOLR-10616: Just read a dev email from Cassandra: "This includes the versions of Tika, ZooKeeper, Log4J, OpenNLP, Velocity, Commons Codec, and Dropwizard today - more can be added if they are needed." > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man >Assignee: Hoss Man >Priority: Major > Fix For: 7.4, master (8.0) > > Attachments: SOLR-10616.patch > > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472565#comment-16472565 ] Mark Miller commented on SOLR-10616: Does this handle things like ZooKeeper version and javadocs now as well? > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man >Assignee: Hoss Man >Priority: Major > Fix For: 7.4, master (8.0) > > Attachments: SOLR-10616.patch > > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427425#comment-16427425 ] ASF subversion and git services commented on SOLR-10616: Commit 6032d6011cedc14ddf2370401cfbd87488ef2b3b in lucene-solr's branch refs/heads/branch_7x from Chris Hostetter [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6032d60 ] SOLR-10616: add 'java-javadocs' as a variable in the ref-guide, and cleanup some overly specific mentions of 'Java 8' Continuation of SOLR-12118 (cherry picked from commit 9009fe6378c8f3fe1757ef744114c3e558919a68) > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man >Priority: Major > Fix For: 7.4, master (8.0) > > Attachments: SOLR-10616.patch > > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427427#comment-16427427 ] ASF subversion and git services commented on SOLR-10616: Commit 9009fe6378c8f3fe1757ef744114c3e558919a68 in lucene-solr's branch refs/heads/master from Chris Hostetter [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9009fe6 ] SOLR-10616: add 'java-javadocs' as a variable in the ref-guide, and cleanup some overly specific mentions of 'Java 8' Continuation of SOLR-12118 > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man >Priority: Major > Fix For: 7.4, master (8.0) > > Attachments: SOLR-10616.patch > > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[
https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426015#comment-16426015
]
Hoss Man commented on SOLR-10616:
-
I've worked up a patch that:
* adds a new {{java-javadocs}} variable for use in our {{*.adoc}} files
* replaces existing hardcoded {{docs.oracle.com/...}} javadoc urls with this
variable
* removes a lot of unneccessarily specific mentions of "java 8" and just refers
to "java" ...
The more I looked into references to "java 8" or "java 1.8" the less convinced
i was that a variable would be useful here. In every case i found, i felt like
either the docs were improved by being less specific, *OR* using a variable
could easily lead to confusion/mistakes if/when we change our minimum version
to java 9 ... in the latter cases, i made a note to revisit those specific
sections in LUCENE-8154.
> use more ant variables in ref guide pages: particular for javadoc &
> third-party lib versions
>
>
> Key: SOLR-10616
> URL: https://issues.apache.org/jira/browse/SOLR-10616
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
>Reporter: Hoss Man
>Priority: Major
> Attachments: SOLR-10616.patch
>
>
> we already use ant variables for the lucene/solr version when building
> lucene/solr javadoc links, but it would be nice if we could slurp in the JDK
> javadoc URLs for the current java version & the versions.properties values
> for all third-party deps as well, so that links to things like the zookeeper
> guide, or the tika guide, or the javadocs for DateInstance would always be
> "current"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420109#comment-16420109 ] Hoss Man commented on SOLR-10616: - thanks for reminding me about this issue Steve. I think the things still outstanding is the java version and the "java" javadoc links ... but i'll try to tackle those soon. > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man >Priority: Major > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420089#comment-16420089 ] Steve Rowe commented on SOLR-10616: --- Is this issue still needed, or was it effectively handled by SOLR-12118 ? > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man >Priority: Major > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045126#comment-16045126 ] Cassandra Targett commented on SOLR-10616: -- bq. the full Solr version, like "6.6.0", for things like the binary package I figured out another way around this, so we can live without it to avoid confusion. bq. the version with an underscore, like "6_6", to automate the sitemap.xml generation I have what I need for this ^^, but we still want some of the other items like ZK version, etc., mentioned in the original description. > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045110#comment-16045110 ] ASF subversion and git services commented on SOLR-10616: Commit 74904dbd66942c49cc7e71d10b61ca09515edbfa in lucene-solr's branch refs/heads/branch_6x from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=74904db ] SOLR-10616: parameterize Guide HTML path in sitemap.xml > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045106#comment-16045106 ] ASF subversion and git services commented on SOLR-10616: Commit f434e34d5c7b33783875e77f919c05f0cd806b3f in lucene-solr's branch refs/heads/master from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f434e34 ] SOLR-10616: parameterize Guide HTML path in sitemap.xml > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10616) use more ant variables in ref guide pages: particular for javadoc & third-party lib versions
[ https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045031#comment-16045031 ] Cassandra Targett commented on SOLR-10616: -- I'd also like a couple more variables to put in the docs: * the full Solr version, like "6.6.0", for things like the binary package * the version with an underscore, like "6_6", to automate the sitemap.xml generation > use more ant variables in ref guide pages: particular for javadoc & > third-party lib versions > > > Key: SOLR-10616 > URL: https://issues.apache.org/jira/browse/SOLR-10616 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Hoss Man > > we already use ant variables for the lucene/solr version when building > lucene/solr javadoc links, but it would be nice if we could slurp in the JDK > javadoc URLs for the current java version & the versions.properties values > for all third-party deps as well, so that links to things like the zookeeper > guide, or the tika guide, or the javadocs for DateInstance would always be > "current" -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
