This is an automated email from the ASF dual-hosted git repository.
cpoerschke pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/main by this push:
new ded24da90e9 dev-docs + help: try-and-tweak 'Solr X Lucene' docs (#2223)
ded24da90e9 is described below
commit ded24da90e97fc7fb10c12ef49ec1ad74d0b4efc
Author: Christine Poerschke <[email protected]>
AuthorDate: Thu Feb 8 12:19:59 2024 +0000
dev-docs + help: try-and-tweak 'Solr X Lucene' docs (#2223)
---
dev-docs/dependency-upgrades.adoc | 4 ++--
dev-docs/lucene-upgrade.md | 4 ++++
help/dependencies.txt | 4 ++--
3 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/dev-docs/dependency-upgrades.adoc
b/dev-docs/dependency-upgrades.adoc
index e26e0cb956d..9f7372cc1bd 100644
--- a/dev-docs/dependency-upgrades.adoc
+++ b/dev-docs/dependency-upgrades.adoc
@@ -22,7 +22,7 @@ Keeping them up-to-date is crucial for a number of reasons:
* minimizing the risk of critical CVE vulnerabilities by staying on a recent
and supported version
* avoiding "dependency hell", that can arise from falling too far behind
-Read the `help/dependencies.txt` file for an in-depth explanation of how
gradle is deployed in Solr, using
+Read the
https://github.com/apache/solr/blob/main/help/dependencies.txt[help/dependencies.txt]
file for an in-depth explanation of how gradle is deployed in Solr, using
https://github.com/palantir/gradle-consistent-versions[Gradle
consistent-versions] plugin.
== Manual dependency upgrades
@@ -56,4 +56,4 @@ choose to change to a less frequent schedule or disable the
bot, by editing `ren
=== Configuring renovate.json
While the bot runs on a
https://github.com/solrbot/renovate-github-action[GitHub repo external to the
project],
the bot behavior can be tailored by editing `.github/renovate.json` in this
project.
-See https://docs.renovatebot.com[Renovatebot docs] for available options.
\ No newline at end of file
+See https://docs.renovatebot.com[Renovatebot docs] for available options.
diff --git a/dev-docs/lucene-upgrade.md b/dev-docs/lucene-upgrade.md
index 9ff683a4cb9..c9ee1a27802 100644
--- a/dev-docs/lucene-upgrade.md
+++ b/dev-docs/lucene-upgrade.md
@@ -80,3 +80,7 @@ gradlew test
Push the local branch to github (fork) and open a pull request.
+## Looking for something else?
+
+Thanks for reading these upgrade steps! But perhaps you were looking for
information on trying out prerelease Lucene changes or joint local Solr and
Lucene development? If so then please see the 'Update Lucene prerelease' and
'Lucene local dependency substitution' sections in the
[help/dependencies.txt](../help/dependencies.txt) documentation.
+
diff --git a/help/dependencies.txt b/help/dependencies.txt
index 8cd78b72334..c1c81c560b0 100644
--- a/help/dependencies.txt
+++ b/help/dependencies.txt
@@ -102,7 +102,7 @@ If you want to upgrade Lucene to a newer build proceed like
the following:
prefixed by '#')
- Edit ./versions.props and change Lucene's version to '9.0.0-prereleaseX',
with 'X' is the jenkins build number
-- Edit ./gradle/defaults.gradle and change jenkins build number, too
+- Edit ./gradle/globals.gradle and change jenkins build number, too
(this directs the repository to the one created by latest build):
def lucenePrereleaseBuild = 'X'
- Run: gradlew --write-locks (as described before)
@@ -134,7 +134,7 @@ Local Maven repository Lucene artifacts (for use with the
"-Plucene.dev.version" project property) may be created by running the
following command from within a local Lucene project:
- gradlew mavenToLocalRepo
+ gradlew mavenToLocal
As is the case with project properties generally, the relevant properties
can be invoked on the command line, or configured via the gradle.properties
