Hi,

we do not ship "storm-kafka-client-*" since a few versions. 
It isn't contained in 2.3.0, 2.4.0, 2.5.0 and 2.6.0 (didn't check the
others), so yes, it is intentional. (It is a collection of spouts /
bolts, trident - so more or less something a user may want to use (or
not)).

The JAR itself is available via Maven:

https://repository.apache.org/content/repositories/orgapachestorm-1110/org/apache/storm/storm-kafka-client/2.6.1/

Hope it helps
Richard


Am Dienstag, dem 30.01.2024 um 16:02 +0100 schrieb Alexandre
Vermeerbergen:
> Other question: to test
> https://issues.apache.org/jira/browse/STORM-4016 I would like to have
> storm-kafka-client--2.6.1.jar, but it's not in
> apache-storm-2.6.1.tar.gz archive (binary artifacts)
> => is that intentional ?
> => from where can I find torm-kafka-client--2.6.1.jar ?
> (sorry if my questions sound trivial..)
> 
> Alexandre
> 
> Le mar. 30 janv. 2024 à 14:12, Richard Zowalla <rich...@zowalla.com>
> a écrit :
> > 
> > Here is the missing link. It is located at the usual location:
> > 
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/
> > 
> > Thx for the hint!
> > 
> > 
> > Am Dienstag, dem 30.01.2024 um 14:09 +0100 schrieb Alexandre
> > Vermeerbergen:
> > > Hi Richard,
> > > 
> > > The link to "Storm Source and Binary Release with sha512
> > > signature
> > > files" is missing, can you please re-send the vote mail ?
> > > 
> > > Thanks,
> > > Alexandre
> > > 
> > > Le mar. 30 janv. 2024 à 09:42, Richard Zowalla <r...@apache.org>
> > > a
> > > écrit :
> > > > 
> > > > Hi ladies & lords,
> > > > 
> > > > I have posted a first release candidate for Apache Storm 2.6.1
> > > > release
> > > > and it is ready for testing.
> > > > 
> > > > We fixed a few bugs and upgraded libraries.
> > > > 
> > > > Full list of changes in this release:
> > > > 
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
> > > > 
> > > > 
> > > > The Nexus staging repository is here:
> > > > 
> > > > 
> > > > https://repository.apache.org/content/repositories/orgapachestorm-1110/
> > > > 
> > > > Storm Source and Binary Release with sha512 signature files are
> > > > here:
> > > > 
> > > > The release artifacts are signed with my key contained in this
> > > > file:
> > > > 
> > > > https://dist.apache.org/repos/dist/release/storm/KEYS
> > > > 
> > > > The release was made from the Apache Storm v2.6.1 tag at:
> > > > 
> > > > https://github.com/apache/storm/releases/tag/v2.6.1
> > > > 
> > > > 
> > > > To use it in a maven build set the version for Storm to 2.6.1
> > > > and
> > > > add
> > > > the following to your POM:
> > > > 
> > > > 
> > > > <repositories>
> > > > <repository>
> > > > <id>storm-2.6.1-rc1</id>
> > > > <name>Testing Storm 2.6.1 RC1 </name>
> > > > <url>
> > > > https://repository.apache.org/content/repositories/orgapachestorm
> > > > -
> > > > 1110/
> > > > 
> > > > </url>
> > > > </repository>
> > > > </repositories>
> > > > 
> > > > 
> > > > The release was made using the Storm release process,
> > > > documented on
> > > > the
> > > > GitHub repository:
> > > > https://github.com/apache/storm/blob/master/RELEASING.md
> > > > 
> > > > Please vote on releasing these packages as Apache Storm 2.6.0.
> > > > 
> > > > The vote is open for at least the next 72 hours or as long as
> > > > needed.
> > > > 
> > > > "How to vote" is described here:
> > > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > > > 
> > > > When voting, please list the actions taken to verify the
> > > > release.
> > > > 
> > > > Only votes from the Storm PMC are binding, but everyone is
> > > > welcome
> > > > to
> > > > check the release candidate and vote.
> > > > 
> > > > The vote passes if at least three binding +1 votes are cast.
> > > > 
> > > > [ ] +1 Release this package as Apache Storm 2.6.1
> > > > [ ]  0 No opinion
> > > > [ ] -1 Do not release this package because...
> > > > 
> > > > Thanks to everyone who contributed to this release.
> > > > 
> > > > Thanks!
> > > > 
> > > > Richard
> > > > 
> > 

Reply via email to