You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicecomb.apache.org by bismy <bi...@qq.com> on 2018/03/27 01:44:26 UTC
回复: Propose adding maven archetypes in Java Chassis
Agreed. We can add a brief readme to each generated projects and write some user guides how to use archetypes.
------------------ 原始邮件 ------------------
发件人: "Zen Lin"<ze...@gmail.com>;
发送时间: 2018年3月26日(星期一) 晚上7:12
收件人: "dev"<de...@servicecomb.apache.org>;
主题: Re: Propose adding maven archetypes in Java Chassis
Thanks to yangyong, to my opinion, I quite agree with you, It should be
useful to users and the community, and what about others's opinion?
2018-03-26 15:07 GMT+08:00 郑扬勇 <ya...@qq.com>:
> Hi Zen Lin:
> If user create a blank maven project and want import chassis, he must
> do these steps:
> 1. Our chassis support multi provider and transport, also support
> integration with spring boot, he must copy right dependencies into pom, and
> let "java-chassis-dependencies" manage versions.
> 2. He must create "microservice.yaml" in resources folder and fill
> right setting, so I think he will copy from samples.
> 3. He may copy endpoint implement and replace the operations for faster
> rewrite.
>
> So, I think if we need write long user guide (
> http://servicecomb.incubator.apache.org/users/) to explain how to do,why
> don't we just create one with a "hello world" provider, then Fire.
>
> These archetypes not only for scaffold, they will act as template
> project(module) for more common use.
>
> What's archetypes : http://maven.apache.org/guides/introduction/
> introduction-to-archetypes.html
> Camel archetypes : http://camel.apache.org/camel-maven-archetypes.html
>
>
> Regards
> yangyong.zheng
>
> ------------------ 原始邮件 ------------------
> 发件人: "Zen Lin"<ze...@gmail.com>;
> 发送时间: 2018年3月26日(星期一) 中午1:01
> 收件人: "dev"<de...@servicecomb.apache.org>;
>
> 主题: Re: Propose adding maven archetypes in Java Chassis
>
>
>
> @ yangyong.zheng,
> I guess you just want archetypes in order to provide scaffolding for
> ServiceComb, can you let us know how others provide there archetypes for
> conventional practice to reach a consistent development habit with others?
>
>
> 2018-03-26 10:15 GMT+08:00 郑扬勇 <ya...@qq.com>:
>
> > Hi All:
> > Although we had provide many samples to show how develop a
> microservice
> > using chassis,I think we must provide some maven archetypes in order to
> > help users start development quickly,including:
> >
> > 1.business-service-pojo
> > Archetype for create a common microservice using pojo provider.
> > 2.business-service-springmvc
> > Archetype for create a common microservice using springmvc provider.
> > 3.business-service-with-spring-boot
> > Archetype for create a common microservice using
> > spring-boot-starter-provider.
> > 4.edge-service
> > Archetype for create an edge microservice using servicecomb
> edge-core
> > with a general router dispatcher.
> > 5.edge-service-with-zuul
> > Archetype for create an edge microservice using spring cloud zuul.
> > 6.auth-service
> > Archetype for create an auth microservice with a simple jwt(Json Web
> > Token) authentication.
> >
> > After we publish these archetypes,uses can generate them by "mvn
> > archetype:generate" and modify further.
> >
> > Regards
> > yangyong.zheng
>