You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shardingsphere.apache.org by "zhangliang@apache.org" <zh...@apache.org> on 2020/01/19 04:33:19 UTC
Split UI and java backend codes
Hi ShardingSphere community,
Our current repo of source code are mix ui and backend coeds. As you know,
there are some disadvantage of this code structure:
- The npm installation is very slow when UI compile.
- The developers have different technical stack of front-end and back-end.
So I plan Split UI and java backend codes. They are still in same repo, but
in different maven projects. And the distribution project should split 2
projects too.
I will do it soon, if anybody think it may cause any problem, please let me
know.
------------------
Liang Zhang (John)
Apache ShardingSphere & Dubbo
Re: Re: Split UI and java backend codes
Posted by "zhangliang@apache.org" <zh...@apache.org>.
Done by issue[1].
[1] https://github.com/apache/incubator-shardingsphere/issues/4024
------------------
Liang Zhang (John)
Apache ShardingSphere & Dubbo
KimmKing <ki...@apache.org> 于2020年1月19日周日 下午8:45写道：
> According to my test, splitting front-end and back-end project codes will
> cut down half the time when a developer only focus on one of it.
> And some points should be consider:
> 1. pom module and project references
> 2. assembly distributions
> 3. jenkins CI and release
>
> 在 2020-01-19 16:13:40，"Sheng Wu" <wu...@gmail.com> 写道：
> >If this is painful, make sense to me. We still keep compiling both in
> >SkyWalking today. :)
> >
> >Sheng Wu 吴晟
> >Twitter, wusheng1108
> >
> >
> >zhangliang@apache.org <zh...@apache.org> 于2020年1月19日周日 下午12:33写道：
> >
> >> Hi ShardingSphere community,
> >>
> >> Our current repo of source code are mix ui and backend coeds. As you
> know,
> >> there are some disadvantage of this code structure:
> >>
> >> - The npm installation is very slow when UI compile.
> >> - The developers have different technical stack of front-end and
> back-end.
> >>
> >> So I plan Split UI and java backend codes. They are still in same repo,
> but
> >> in different maven projects. And the distribution project should split 2
> >> projects too.
> >>
> >> I will do it soon, if anybody think it may cause any problem, please
> let me
> >> know.
> >>
> >> ------------------
> >>
> >> Liang Zhang (John)
> >> Apache ShardingSphere & Dubbo
> >>
>
Re:Re: Split UI and java backend codes
Posted by KimmKing <ki...@apache.org>.
According to my test, splitting front-end and back-end project codes will cut down half the time when a developer only focus on one of it.
And some points should be consider:
1. pom module and project references
2. assembly distributions
3. jenkins CI and release
在 2020-01-19 16:13:40，"Sheng Wu" <wu...@gmail.com> 写道：
>If this is painful, make sense to me. We still keep compiling both in
>SkyWalking today. :)
>
>Sheng Wu 吴晟
>Twitter, wusheng1108
>
>
>zhangliang@apache.org <zh...@apache.org> 于2020年1月19日周日 下午12:33写道：
>
>> Hi ShardingSphere community,
>>
>> Our current repo of source code are mix ui and backend coeds. As you know,
>> there are some disadvantage of this code structure:
>>
>> - The npm installation is very slow when UI compile.
>> - The developers have different technical stack of front-end and back-end.
>>
>> So I plan Split UI and java backend codes. They are still in same repo, but
>> in different maven projects. And the distribution project should split 2
>> projects too.
>>
>> I will do it soon, if anybody think it may cause any problem, please let me
>> know.
>>
>> ------------------
>>
>> Liang Zhang (John)
>> Apache ShardingSphere & Dubbo
>>
Re: Split UI and java backend codes
Posted by Sheng Wu <wu...@gmail.com>.
If this is painful, make sense to me. We still keep compiling both in
SkyWalking today. :)
Sheng Wu 吴晟
Twitter, wusheng1108
zhangliang@apache.org <zh...@apache.org> 于2020年1月19日周日 下午12:33写道：
> Hi ShardingSphere community,
>
> Our current repo of source code are mix ui and backend coeds. As you know,
> there are some disadvantage of this code structure:
>
> - The npm installation is very slow when UI compile.
> - The developers have different technical stack of front-end and back-end.
>
> So I plan Split UI and java backend codes. They are still in same repo, but
> in different maven projects. And the distribution project should split 2
> projects too.
>
> I will do it soon, if anybody think it may cause any problem, please let me
> know.
>
> ------------------
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>