Re: Moving hessian-lite from Dubbo codebase to eco-system

+1 We could delay and close it first. At an appropriate time reopen it. On Mon, Jun 11, 2018 at 5:46 PM, Ian Luo wrote: > Hi Jerrick & others, > > Since hessian-lite module is now moved out into dubbo group, should we > close issue#1701[1], one part of our code coverage project [2]? > >

Re: Moving hessian-lite from Dubbo codebase to eco-system

Hi Jerrick & others, Since hessian-lite module is now moved out into dubbo group, should we close issue#1701[1], one part of our code coverage project [2]? Regards, -Ian. 1. https://github.com/apache/incubator-dubbo/issues/1701 2. https://github.com/apache/incubator-dubbo/projects/1 On Thu,

Re: Moving hessian-lite from Dubbo codebase to eco-system

After discussing, we are about to do this in next major version, which is 2.7.x. The corresponding issue has also been created on github: https://github.com/apache/incubator-dubbo/issues/1778 On Thu, May 17, 2018 at 2:29 PM, Mercy wrote: > Please do it since 2.7.x! > > > > 在 2018/5/16 上午11:11,

Re: Moving hessian-lite from Dubbo codebase to eco-system

Please do it since 2.7.x! 在 2018/5/16 上午11:11, Jun Liu 写道: Now we are considering that moving it to Dubbo eco-system, which is https://github/dubbo. How do you think about this? I agree with moving hessian-lite to the dubbo eco-system. If we do that, we may need to upgrade the core dubbo

Re: Moving hessian-lite from Dubbo codebase to eco-system

> Now we are considering that moving it to Dubbo eco-system, which is > https://github/dubbo. > > How do you think about this? I agree with moving hessian-lite to the dubbo eco-system. If we do that, we may need to upgrade the core dubbo version to 2.7.x to identify incompatible usage of

Re: Moving hessian-lite from Dubbo codebase to eco-system

> What do the owner / maintainers of hessian-lite think about that? Is there > any need to fork their version? Actually, the dubbo team is the official maintainer of hessian-lite, it’s always been published along side with dubbo. There are mainly 2 reasons for maintaining an additional

Re: Moving hessian-lite from Dubbo codebase to eco-system

Agree +1> Now we are considering that moving it to Dubbo eco-system, which is https://github/dubbo. The hessian-lit sub module is a serialize component of the same level as Thrift, and should be placed outside the core system. Xin Wang lovep...@hotmail.com 在

Re: Moving hessian-lite from Dubbo codebase to eco-system

1. Can you just use their released version? Internal version has fixed a lot of bugs, there is an incompatibility risk when using the release version in the short term. Before using the release version, we need to submit the repaired feature to owner / maintainers of hessian-lit. yiji > 在

Re: Moving hessian-lite from Dubbo codebase to eco-system

Hi, > Now we are considering that moving it to Dubbo eco-system, which is > https://github/dubbo. > > How do you think about this? I don’t know the history here so the answer to these questions may be obvious to someone eon the project. What do the owner / maintainers of hessian-lite think