It makes sense.
zhaojun 于2019年5月30日周四 下午5:32写道：
> We have make the scope is ‘provided’, it will not be included while
> release.
>
> --
> Zhao Jun
> Apache Sharding-Sphere & ServiceComb
>
> > On May 30, 2019, at 4:37 PM, Zheng Feng wrote:
> >
> > Well, it looks good to me but I
We have make the scope is ‘provided’, it will not be included while release.
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On May 30, 2019, at 4:37 PM, Zheng Feng wrote:
>
> Well, it looks good to me but I have to mention that the Narayana is LGPL
> license and I think you
Well, it looks good to me but I have to mention that the Narayana is LGPL
license and I think you have to exclude this artifact when doing the
release.
zhaojun 于2019年5月30日周四 上午9:32写道：
> Hi, zheng
>
> FYI, I have moved sharding-transaction-xa-narayana to our dev branch.
>
> You can see here:
>
>
We can enjoy the new feature of JDK 8, and as Sheng Wu said, updating to
JDK 8 is not difficult. After we listen to voices of SharingSphere
community, i think it is better to upgrade.
My +1 to upgrade.
-
Juan Pan (Trista)
Apache ShardingSphere
Talk with the community users, if they are ok to accept JDK 8, do it as soon as
possible.
Upgrade to JDK 8, don’t mean you have to follow JDK coding features at the
beginning.
It should be easy to do.
Sheng Wu
Apache Skywalking, ShardingSphere, Zipkin
> 在 2019年5月30日，下午3:15，zhaojun 写道：
>
>
Hi
If the community supports to upgrade to JDK 8, which makes sense to me,
I highly recommend to do it before stable version release.
Change this in 4.0 -> 4.1 as a break update, for a library, it looks like
strange.
My +1 to upgrade now.
Sheng Wu
Apache Skywalking, ShardingSphere, Zipkin
Hi,
JDK 7 is deprecated for long time by official, more and more applications
are using JDK 8 as their Java compile environment.
Some dependencies of ShardingSphere are using JDK 8 also, such as Etcd,
ServiceComb, Seata and new version of Guava, so I plan upgrade to JDK 8
after 4.0.0 stable
