You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2022/06/29 12:44:00 UTC
[jira] [Created] (LUCENE-10631) Consolidate java version numbers in one place and reuse them across build parts
|  |
[Dawid
Weiss](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dweiss)
**created** an issue
---|---
|
---
| [Lucene - Core](https://issues.apache.org/jira/browse/LUCENE) / [](https://issues.apache.org/jira/browse/LUCENE-10631)
[LUCENE-10631](https://issues.apache.org/jira/browse/LUCENE-10631)
---
[Consolidate java version numbers in one place and reuse them across build
parts](https://issues.apache.org/jira/browse/LUCENE-10631)
| Issue Type: |  Sub-task
---|---
Assignee: | Unassigned
Created: | 29/Jun/22 12:43
Priority: |  Minor
Reporter: | [Dawid
Weiss](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dweiss)
|
[R. Muir/ mailing list discussions]
Ideally we could consolidate a lot of them in a simple .properties file that
contains the min/max major version numbers. could be then sucked in by:
* gradle logic
* java logic such as checks done in WrapperDownloader
* bash logic such as error messaging in ./gradlew.sh
* python smoketester logic?
---
| | [ 
](https://issues.apache.org/jira/browse/LUCENE-10631#add-comment "Add
Comment") | [Add
Comment](https://issues.apache.org/jira/browse/LUCENE-10631#add-comment "Add
Comment")
---|---
| This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9) | |

---