Re: [PROPOSAL] ServiceComb connects SpringCloud
Hi, everyone The client of service-center is ready. And the API provided by the client is placed on JIRA ( https://issues.apache.org/jira/browse/SCB-1529 ) for discussion . On 10/11/2019 10:06，zhouzhongyuan96 wrote： Hi, everyone After some related discussions, I thought about this matter carefully. My current plan is to prioritize the development of two Java language common clients that are connected to servicecomb-service-center and servicecomb-kie respectively in the ServiceComb project. The development plan for the components that connect to SpringCloud will be considered later. On 10/10/2019 16:58，zhouzhongyuan96 wrote： Hi, Xiaoliang In fact, I would like to implement a ServiceComb connection to SpringCloud tool in servicecomb-toolkit, including Java clients for service-center and kie, as well as spring-cloud-servicecomb-service-center and spring-cloud-servicecomb-kie component, and may do more in the future. On 10/10/2019 16:17，Xiaoliang Tian wrote： this is a awesome proposal, in fact we already have connected spring cloud to servicecomb, service center is finished by ourself, https://github.com/huaweicloud/spring-cloud-huawei you can directly use it. for kie you can develop the java client and spring cloud components, that would also helps a lot to our ecosystem. the Java client for kie, you can contribute to https://github.com/apache/servicecomb-kie. the spring-cloud-servicecomb-kie component, I recommand you contribute to https://github.com/huaweicloud/spring-cloud-huawei.
Re: [VOTE] Release Apache ServiceComb Kie version 0.1.0
Sorry, Seems I checked the wrong source tar ball from github releases. I re-checked the source release from the apache dist server. It's OK. On Tue, Oct 22, 2019 at 11:09 AM Yang Bo wrote: > +1 > > I checked the build process from the v0.1.0.tar.gz source release and it's > OK. > > Some minor issues: > 1. The source tar ball should contain full product name along with > version. It should be servicecomb-kie-v0.1.0.tar.gz. > 2. The uncompressed folder name for source release should also follow the > semVer convention. So it should be servicecomb-kie-v0.1.0. Currently the > 'v' is missing. > 3. The licenses folder is for binary release thus should be removed from > the source release. > > On Mon, Oct 21, 2019 at 8:38 PM Xiaoliang Tian > wrote: > >> Hi All, >> >> This is a call for Vote to release Apache ServiceComb Kie version 0.1.0 >> >> Release Candidate : >> >> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-kie/0.1.0/rc-03/ >> >> >> >> Release Tag : >> https://github.com/apache/servicecomb-kie/releases/tag/v0.1.0 >> >> Release CommitID: 65ead3641f33c02055d4365020736d7b4cf34779 >> >> Release Notes : >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345632 >> >> Keys to verify the Release Candidate : >> https://dist.apache.org/repos/dist/dev/servicecomb/KEYS >> >> Voting will start now ( Monday, 21nd October , 2019) and will remain open >> for at-least 72 hours, Request all PMC members to give their vote. >> >> [ ] +1 Release this package as 0.1.0 >> [ ] +0 No Opinion >> [ ] -1 Do not release this package because >> >> On the behalf of ServiceComb Team >> >> >> Best Wishes & Regards >> > > > -- > Best Regards, > Yang. > -- Best Regards, Yang.
Re: [VOTE] Release Apache ServiceComb Kie version 0.1.0
+1 I checked the build process from the v0.1.0.tar.gz source release and it's OK. Some minor issues: 1. The source tar ball should contain full product name along with version. It should be servicecomb-kie-v0.1.0.tar.gz. 2. The uncompressed folder name for source release should also follow the semVer convention. So it should be servicecomb-kie-v0.1.0. Currently the 'v' is missing. 3. The licenses folder is for binary release thus should be removed from the source release. On Mon, Oct 21, 2019 at 8:38 PM Xiaoliang Tian wrote: > Hi All, > > This is a call for Vote to release Apache ServiceComb Kie version 0.1.0 > > Release Candidate : > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-kie/0.1.0/rc-03/ > > > > Release Tag : > https://github.com/apache/servicecomb-kie/releases/tag/v0.1.0 > > Release CommitID: 65ead3641f33c02055d4365020736d7b4cf34779 > > Release Notes : > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345632 > > Keys to verify the Release Candidate : > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > Voting will start now ( Monday, 21nd October , 2019) and will remain open > for at-least 72 hours, Request all PMC members to give their vote. > > [ ] +1 Release this package as 0.1.0 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > On the behalf of ServiceComb Team > > > Best Wishes & Regards > -- Best Regards, Yang.
[VOTE] Release Apache ServiceComb Kie version 0.1.0
Hi All, This is a call for Vote to release Apache ServiceComb Kie version 0.1.0 Release Candidate : https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-kie/0.1.0/rc-03/ Release Tag : https://github.com/apache/servicecomb-kie/releases/tag/v0.1.0 Release CommitID: 65ead3641f33c02055d4365020736d7b4cf34779 Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345632 Keys to verify the Release Candidate : https://dist.apache.org/repos/dist/dev/servicecomb/KEYS Voting will start now ( Monday, 21nd October , 2019) and will remain open for at-least 72 hours, Request all PMC members to give their vote. [ ] +1 Release this package as 0.1.0 [ ] +0 No Opinion [ ] -1 Do not release this package because On the behalf of ServiceComb Team Best Wishes & Regards
Re: Swagger Codegen
Hi William， Thanks for your information. It's good to know there are some new features of OpenAPI Generator. Current we are leverage OpenAPI to do the contract first web service development, and we just upgrade to use OpenAPI V3 in the toolkit. I'm not the writer of toolkit, so I just forward the mail to the dev@servicecomb, maybe Sun LiShen can answer your questions. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Oct 21, 2019 at 12:35 AM William Cheng wrote: > > Hi, > > Understood that you're busy. I've an important news to share with you: > > In May 2018, myself and other top contributors (40+) have decided to fork > Swagger Codegen to maintain a community-driven version called "OpenAPI > Generator" (https://openapi-generator.tech), which supports both > OpenAPI/Swagger spec v2 and v3. > > For the reasons behind the fork, please refer to the Q: > https://github.com/OpenAPITools/openapi-generator/blob/master/docs/qna.md. > For migration, please refer to > https://github.com/OpenAPITools/openapi-generator/blob/master/docs/migration-from-swagger-codegen.md > > 2 weeks ago we released OpenAPI Generator v4.1.3 with 4 new generators - > https://twitter.com/oas_generator/status/1180123829626003456. Please check it > out and let us know if you've any feedback or questions. > > Best regards, > William > https://github.com/wing328 > > On Fri, 18 Oct 2019 at 02:14, William Cheng wrote: >> >> Hi Willem, >> >> Sorry for reaching out to you directly. I saw you using Swagger Codegen: >> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L357 >> >> I'm the top contributor to Swagger Codegen. May I know how's your experience >> with Swagger Codegen so far? Did you find it easy to use and customize? >> >> Best regards, >> William >> https://github.com/wing328
