[
https://issues.apache.org/jira/browse/KAFKA-15110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hudeqi updated KAFKA-15110:
---------------------------
Description:
For example, when I build a jar through './gradlew jar' under a 3.5.0 branch,
and then switch to a 3.6.0 branch, a jar is also built. Since "core/build/libs"
is a "gitignore dir", there will be two versions of packages in this
directory. At this time, when I start the kafka process under the local bin
dir, I will encounter the problem that it cannot be started because the version
is running incorrectly.
The reason is that /kafka-run-class.sh transfers all jar packages to CLASSPATH
by default, which is an unreasonable behavior.
For details, see the attached screenshot below:
Figure 1 shows that the abnormal exit because of the missing of
ProducerStateManagerConfig(int xx) method, which is defined in version 3.5.0,
but the initial method of ProducerStateManagerConfig in version 3.6.0 has two
parameters.
Figure 2 is the printed value of CLASSPATH.
> Wrong version may be run, which will cause to fail to run when there are
> multiple version jars under core/build/libs
> --------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-15110
> URL: https://issues.apache.org/jira/browse/KAFKA-15110
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.4.1
> Reporter: hudeqi
> Assignee: hudeqi
> Priority: Major
>
> For example, when I build a jar through './gradlew jar' under a 3.5.0 branch,
> and then switch to a 3.6.0 branch, a jar is also built. Since
> "core/build/libs" is a "gitignore dir", there will be two versions of
> packages in this directory. At this time, when I start the kafka process
> under the local bin dir, I will encounter the problem that it cannot be
> started because the version is running incorrectly.
> The reason is that /kafka-run-class.sh transfers all jar packages to
> CLASSPATH by default, which is an unreasonable behavior.
> For details, see the attached screenshot below:
> Figure 1 shows that the abnormal exit because of the missing of
> ProducerStateManagerConfig(int xx) method, which is defined in version 3.5.0,
> but the initial method of ProducerStateManagerConfig in version 3.6.0 has two
> parameters.
> Figure 2 is the printed value of CLASSPATH.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
