[
https://issues.apache.org/jira/browse/STORM-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bipin Prasad resolved STORM-3912.
---------------------------------
Resolution: Fixed
PR Merged by vsense
> Pull new carbonite code into storm
> ----------------------------------
>
> Key: STORM-3912
> URL: https://issues.apache.org/jira/browse/STORM-3912
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-clojure
> Reporter: Bipin Prasad
> Assignee: Bipin Prasad
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The artifact com.twitter.carbonite:1.5 was last changed 10 years ago. The jar
> is available from clojars.org and as per pom file, the source code resides in
> a personal github repo not affiliated with twitter.
> This jar depends on Kryo 3 and has java class format 1.6, and clojure 1.5.
> These need to be changed. storm-clohure module depends on carbonite jar to
> register classes into Kryo.
> Pull the source code into storm-clojure-carbonite so that it can be modified
> as long as clojure is supported in Storm.
>
> Carbonite Code Details:
> * Carbonite version 1.5 pom file shows code url as
> [https://github.com/sritchie/carbonite.] This code was forked from
> [https://github.com/revelytix/carbonite.] Both these are inactive.
> * Carbonite version 1.6 resides at
> [https://github.com/bipinprasad/carbonite.] This code was forked from
> [https://github.com/sritchie/carbonite|https://github.com/sritchie/carbonite.]
> (the source for Carbonite 1.5). Version 1.6 was created after changing the
> JVM and Kryo and Chill dependencies. The jar was published to
> [https://clojars.org.|https://clojars.org./]
> * Steps to move code away from personal github account:
> ** Fork Code from
> [https://github.com/sritchie/carbonite|https://github.com/sritchie/carbonite.]
> ** Determine new maven/clojar location for the jar
> ** Obtain proper permission for the maven or clojar group (reverse domain)
> ** Get userid/publishing and signing key
> ** Update project.clj ":repositories" tag.
> ** Follow "similar" steps in signing and publishing code as in Storm release
> *** create GPG signing key
> *** sign the jar and pom files (creating .asc files)
> *** use "lein deploy clojars" or "lein deploy maven" to publish
> * Carbonite depends on "chill". One open pull request discussion in that
> project from Jan 7, 2021 is here [https://github.com/twitter/chill/pull/514]
> (Kryo 5). There is some reference to carbonite and Storm.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
