You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by John Fang <xi...@alibaba-inc.com> on 2016/04/05 17:50:29 UTC

答复: why don't we relocate the kryo by maven-shade-plugin?

Than you Bobby,  we'd better not to expose kryo to the end users directly. Of course, there was nothing we could do due to  <http://www.baidu.com/link?url=UKEUbGy68xh0OGoYdgUwU7sS5i3rWWRCxtUo1c9KjIsWYRdn3ts1vU2N1nQjtX2j2WApyi0iZJbemm6UIcjz1w67AfXIjPR_bGqiqzso8nh99ulhWgTrpDCp37mUp0bn> historical reason.

 

发件人: Bobby Evans [mailto:evans@yahoo-inc.com] 
发送时间: 2016年4月5日 22:50
收件人: dev@storm.apache.org; John Fang
主题: Re: why don't we relocate the kryo by maven-shade-plugin?

 

Because we expose kryo to the end users.  They can add in their own plugins to serialize objects and if we shade it all of that will break.

 

- Bobby 

 

On Tuesday, April 5, 2016 9:40 AM, John Fang <xi...@alibaba-inc.com> wrote:

 

  why don't we relocate the kryo by maven-shade-plugin? Due to the carbonite
? The conflict with kryo’s version happened sometime.



Regards

John Fang