Hey Ismael, I checked out a clean copy of Kafka and reuploaded artifacts for 2.1.0-rc1 without code change. There are still those new files in https://repository.apache.org/content/groups/staging/org/apache/kafka/kafka_2.12/2.1.0. I compared 2.0 and 2.1 branch but did not find any suspicious change in release.py and build.gradle.
Since doing a new release could not address this right away and there is no known impact on user due to these redundant files, I am inclined to still release 2.1.0-rc1 so that user can start to use the new features soon. What do you think? Thanks, Dong On Mon, Nov 19, 2018 at 2:16 AM Dong Lin <lindon...@gmail.com> wrote: > Hey Ismael, > > Thanks much for catching this! Sorry I didn't catch this issue before. > > These files were uploaded by release.py scrip in the repo. kafka_2.12-2.1. > 0.mapping contains the following string and the other files are the > signature and hash of the file kafka_2.12-2.1.0.mapping: > > > /home/dolin/research/kafka/.release_work_dir/kafka/core/build/libs/kafka_2.12-2.1.0.jar > > /home/dolin/research/kafka/.release_work_dir/kafka/core/build/tmp/scala/compilerAnalysis/compileScala.analysis > > It is weird to have these files.. Let me generate another release > candidate and try to fix this issue. > > Thanks, > Dong >
