Alexandre, You can download RC3 "source", and build with "mvn clean install" to install artifacts locally, so that Maven recognizes Storm 1.1.0 artifacts from local Maven repo. You may want to remove them from local Maven repo after Storm 1.1.0 is officially released.
If you need to copy artifact jars to some place, you can copy them from target directory of each module. Hope this helps. Thanks, Jungtaek Lim (HeartSaVioR) 2017년 3월 22일 (수) 오후 3:31, Alexandre Vermeerbergen <avermeerber...@gmail.com>님이 작성: > Hello, > > We have our homebrewed tool for compiling our code, and "linking it > against" third party JAR files. > > We have customized this tool to create "big .jar files" corresponding to > our storm topologies. > > The idea is that we checkin all the third party dependencies of a given > release of our applications into our own SCM system, so that we can rebuild > at any time with dependencies located on remote sites. > > But maybe my question wasn't clear enough: is there an HOWTO which explains > how to build the storm-kafka JAR file corresponding to current (1.1.0 rc3) > release, which I need to validate Storm 1.1.0 rc3 against our applications. > > Best regards, > Alexandre Vermeerbergen > > 2017-03-21 23:37 GMT+01:00 P. Taylor Goetz <ptgo...@gmail.com>: > > > Hi Alexandre, > > > > If you don't mind me asking, what is your process for creating your > > topology jars? > > > > Once a release is approved, all artifacts are available in the Maven > > mirrors and can be downloaded with a curl command or a browser. You will > > still have to deal with transient dependencies, which is why we > recommend a > > build system with dependency management (maven, gradle, etc.). > > > > I agree that this change could be better documented. > > > > -Taylor > > > > > On Mar 21, 2017, at 6:08 PM, Alexandre Vermeerbergen < > > avermeerber...@gmail.com> wrote: > > > > > > Hello, > > > > > > Unlike with Storm 1.1.0 RC2, storm-kafka-1.1.0.jar is missing from > > > /external/storm-kafka > > > > > > This directory only contains README.md, which doesn't explains how to > get > > > storm-kafka-1.1.0.jar. > > > > > > Would it be possible to have some detailled instructions on how to > build > > > storm-kafka-1.1.0.jar starting with Storm 1.1.0 release? Please note > that > > > we're not using maven to build our code, hence the need of this JAR. > > > > > > Best regards, > > > Alexandre Vermeerbergen > > > > > > > > > > > > 2017-03-21 20:26 GMT+01:00 P. Taylor Goetz <ptgo...@apache.org>: > > > > > >> This is a call to vote on releasing Apache Storm 1.1.0 (rc3) > > >> > > >> Full list of changes in this release: > > >> > > >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_ > > >> plain;f=CHANGELOG.md;h=68fbab3c4f91359bd397d93a157830542839b002;hb= > > >> e40d213de7067f7d3aa4d4992b81890d8ed6ff31 > > >> > > >> The tag/commit to be voted upon is v1.1.0: > > >> > > >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h= > > >> 7fa62404feb6b86b3143c851b46237580720eb6b;hb= > > e40d213de7067f7d3aa4d4992b8189 > > >> 0d8ed6ff31 > > >> > > >> The source archive being voted upon can be found here: > > >> > > >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1. > > >> 1.0-rc3/apache-storm-1.1.0-src.tar.gz > > >> > > >> Other release files, signatures and digests can be found here: > > >> > > >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.0-rc3/ > > >> > > >> The release artifacts are signed with the following key: > > >> > > >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_ > > >> plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd > > >> > > >> The Nexus staging repository for this release is: > > >> > > >> > https://repository.apache.org/content/repositories/orgapachestorm-1047 > > >> > > >> Please vote on releasing this package as Apache Storm 1.1.0. > > >> > > >> When voting, please list the actions taken to verify the release. > > >> > > >> This vote will be open for at least 72 hours. > > >> > > >> [ ] +1 Release this package as Apache Storm 1.1.0 > > >> [ ] 0 No opinion > > >> [ ] -1 Do not release this package because... > > >> > > >> Thanks to everyone who contributed to this release. > > >> > > >> -Taylor > > >
