[
https://issues.apache.org/jira/browse/IGNITE-28740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-28740:
------------------------------------
Description:
Currently, a new Ignite version is generated for each Ignite instance running
in a separate JVM (see org.apache.ignite.internal.IgniteVersionUtils).
This makes it impossible to compare Ignite instance versions in tests with
multiple JVMs.
We currently have dozens of static version-related parameters that are
duplicated. The logic for calculating the full version is also duplicated
several times.
was:
Currently, a new Ignite version is generated for each Ignite instance running
in a separate JVM (see org.apache.ignite.internal.IgniteVersionUtils).
This makes it impossible to compare Ignite instance versions in multiJVM tests.
> Refactor Ignite product version initialization and usages
> ---------------------------------------------------------
>
> Key: IGNITE-28740
> URL: https://issues.apache.org/jira/browse/IGNITE-28740
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, a new Ignite version is generated for each Ignite instance running
> in a separate JVM (see org.apache.ignite.internal.IgniteVersionUtils).
> This makes it impossible to compare Ignite instance versions in tests with
> multiple JVMs.
> We currently have dozens of static version-related parameters that are
> duplicated. The logic for calculating the full version is also duplicated
> several times.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
