[
https://issues.apache.org/jira/browse/SOLR-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569704#comment-14569704
]
Hoss Man commented on SOLR-7627:
--------------------------------
straw man proposal for automation:
* Commit some new file MAJOR_DEPS_VERSIONS_TEMPLATE.txt and
MAJOR_DEPS_VERSIONS.txt to svn
* the "TEMPLATE" file should list the names of the "major" deps we care about,
along with a variable for the version that matches what we use in ivy. it can
also have a header explaining what the file is for example...{noformat}
This file is used to generate MAJOR_DEPS_VERSIONS.txt when "ant jar-checksum"
is run
Everything above the "CUT" line will be removed when this file is processed
---CUT---
Versions of Major Components
---------------------
Apache Tika ${/org.apache.tika/tika-core}
Jetty ${/org.eclipse.jetty/jetty-server}
...
{noformat}
* modify the {{ant jar-checksums}} so that after rebuilding each of the
checksum files, it also rebuilds MAJOR_DEPS_VERSIONS.txt from the
MAJOR_DEPS_VERSIONS_TEMPLATE.txt file using the same version variables.
* update the build scripts to ensure MAJOR_DEPS_VERSIONS.txt is included in the
binary releases. source releases should include both files.
* update the CHANGES.txt file to refer people to the new
MAJOR_DEPS_VERSIONS.txt file.
> Either automate or stop listing the "Versions of Major Components" in
> CHANGES.txt
> ---------------------------------------------------------------------------------
>
> Key: SOLR-7627
> URL: https://issues.apache.org/jira/browse/SOLR-7627
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> At some point along the way, we got in the practice of having a "Versions of
> Major Components" sub-section in changes.txt for each release ... in addition
> to the normal practice of recording the individual Jiras when deps are
> upgraded.
> maintaining this sub-section accurately seems very tedious and error prone
> (see SOLR-7626) so it seems like we should either:
> * stop doing this completely and trust the users to look at the ivy files for
> the dependencies
> * find a way to automate this so we don't have to do it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
