Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
oh, you need to put the cse maven repo[1] into your maven setting.xml like this. But I think we can add it into the root pom.xml [1]https://github.com/huaweicse/cse-java-chassis-samples/blob/master/HouseAppWithSpringBoot2/settings.xml Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Apr 8, 2019 at 12:07 PM zhang_...@boco.com.cn wrote: > > Hi @bismy @Willem Jiang > > I tried to specify the spring boot version to 2.0.4 in my hotel project. The > following error occurred during startup. This error is due to > spring-cloud-starter-consul-discovery 2.1.1 and spring boot 2.0.4 > Incompatible. > > . ___ _ _ > /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ > ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ > \\/ ___)| |_)| | | | | || (_| | ) ) ) ) > ' || .__|_| |_|_| |_\__, | / / / / > =|_|==|___/=/_/_/_/ > :: Spring Boot ::(v2.0.4.RELEASE) > > 11:49:30.560 [main] INFO org.apache.servicecomb.pack.demo.hotel.Application > - No active profile set, falling back to default profiles: default > java.lang.AbstractMethodError > at > org.springframework.core.OrderComparator.findOrder(OrderComparator.java:84) > at > org.springframework.core.annotation.AnnotationAwareOrderComparator.findOrder(AnnotationAwareOrderComparator.java:65) > at > org.springframework.core.OrderComparator.getOrder(OrderComparator.java:72) > at > org.springframework.core.OrderComparator.getOrder(OrderComparator.java:67) > at > org.springframework.core.OrderComparator.doCompare(OrderComparator.java:38) > at > org.springframework.core.OrderComparator.compare(OrderComparator.java:27) > at java.util.TimSort.countRunAndMakeAscending(TimSort.java:360) > at java.util.TimSort.sort(TimSort.java:220) > at java.util.Arrays.sort(Arrays.java:1512) > at java.util.ArrayList.sort(ArrayList.java:1462) > at > org.springframework.boot.SpringApplication.asUnmodifiableOrderedSet(SpringApplication.java:1325) > at > org.springframework.boot.SpringApplication.getListeners(SpringApplication.java:1234) > at > org.springframework.boot.context.event.EventPublishingRunListener.contextLoaded(EventPublishingRunListener.java:85) > at > org.springframework.boot.SpringApplicationRunListeners.contextLoaded(SpringApplicationRunListeners.java:66) > at > org.springframework.boot.SpringApplication.prepareContext(SpringApplication.java:394) > at > org.springframework.boot.SpringApplication.run(SpringApplication.java:328) > at > org.springframework.boot.SpringApplication.run(SpringApplication.java:1258) > at > org.springframework.boot.SpringApplication.run(SpringApplication.java:1246) > at > org.apache.servicecomb.pack.demo.hotel.Application.main(Application.java:28) > > > But I didn't reproduce LiuBao's error. Please tell me the spring boot version > used by project HouseAppWithSpringBoot2, I tried to compile > HouseAppWithSpringBoot2 but the prompt is as follows > > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > [ERROR] Non-resolvable import POM: Failure to find > com.huawei.paas.cse:cse-dependency-spring-boot2:pom:2.3.62 in > https://repo.maven.apache.org/maven2 was cached in the local repository, > resolution will not be reattempted until the update interval of central has > elapsed or updates are forced @ line 34, column 19 > > > Thanks, > Zhang Lei. > > > > > 在 2019年4月5日，下午4:51，bismy 写道： > > > > I tried following command and resolved the problem: > > > > java -Dspring.profiles.active=mysql -Dloader.path=./libs > > -Dalpha.server.host=0.0.0.0 -Dalpha.server.port=7080 -Dserver.port=6090 > > -Dalpha.cluster.address=localhost:7080 > > -D"spring.datasource.url=jdbc:mysql://localhost:3306/saga?useSSL=false=Asia/Shanghai=utf8" > > -Dspring.datasource.username=root -Dspring.datasource.password=root -jar > > alpha-server-0.4.0-exec.jar > > > > Some problems I met when I try to running alpha, I attached to the mail. > > Some configurations are not mentioned in docs, so it takes quite an effort > > to fix it. > > > > Now I meed another problem, after I changing omega from 0.3.0 to 0.4.0, I > > got following error ( demo is here: > > https://github.com/huaweicse/cse-java-chassis-samples/tree/master/HouseAppWithSpringBoot2). > > > > 2019-04-04 15:54:45.179 INFO 5668 --- [ntloop-thread-0] > > c.h.p.f.auth.credentials.AKSKManager : The application missing project > > infomation, so choose a nearest one [cn-north-1] > > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > > creating bean with name 'compensableAnnotationProcessor' defined in class > > path resource > > [org/apache/servicecomb/pack/omega/transaction/spring/TransactionAspectConfig.class]: > > Unsatisfied dependency expressed through method > > 'compensableAnnotationProcessor' parameter 0; nested exception is > > org.springframework.beans.factory.NoSuchBeanDefinitionException: No > >
Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
Hi @bismy @Willem Jiang
I tried to specify the spring boot version to 2.0.4 in my hotel project. The
following error occurred during startup. This error is due to
spring-cloud-starter-consul-discovery 2.1.1 and spring boot 2.0.4 Incompatible.
. ___ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' || .__|_| |_|_| |_\__, | / / / /
=|_|==|___/=/_/_/_/
:: Spring Boot ::(v2.0.4.RELEASE)
11:49:30.560 [main] INFO org.apache.servicecomb.pack.demo.hotel.Application -
No active profile set, falling back to default profiles: default
java.lang.AbstractMethodError
at
org.springframework.core.OrderComparator.findOrder(OrderComparator.java:84)
at
org.springframework.core.annotation.AnnotationAwareOrderComparator.findOrder(AnnotationAwareOrderComparator.java:65)
at
org.springframework.core.OrderComparator.getOrder(OrderComparator.java:72)
at
org.springframework.core.OrderComparator.getOrder(OrderComparator.java:67)
at
org.springframework.core.OrderComparator.doCompare(OrderComparator.java:38)
at org.springframework.core.OrderComparator.compare(OrderComparator.java:27)
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:360)
at java.util.TimSort.sort(TimSort.java:220)
at java.util.Arrays.sort(Arrays.java:1512)
at java.util.ArrayList.sort(ArrayList.java:1462)
at
org.springframework.boot.SpringApplication.asUnmodifiableOrderedSet(SpringApplication.java:1325)
at
org.springframework.boot.SpringApplication.getListeners(SpringApplication.java:1234)
at
org.springframework.boot.context.event.EventPublishingRunListener.contextLoaded(EventPublishingRunListener.java:85)
at
org.springframework.boot.SpringApplicationRunListeners.contextLoaded(SpringApplicationRunListeners.java:66)
at
org.springframework.boot.SpringApplication.prepareContext(SpringApplication.java:394)
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:328)
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1258)
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1246)
at
org.apache.servicecomb.pack.demo.hotel.Application.main(Application.java:28)
But I didn't reproduce LiuBao's error. Please tell me the spring boot version
used by project HouseAppWithSpringBoot2, I tried to compile
HouseAppWithSpringBoot2 but the prompt is as follows
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Non-resolvable import POM: Failure to find
com.huawei.paas.cse:cse-dependency-spring-boot2:pom:2.3.62 in
https://repo.maven.apache.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced @ line 34, column 19
Thanks,
Zhang Lei.
> 在 2019年4月5日，下午4:51，bismy 写道：
>
> I tried following command and resolved the problem:
>
> java -Dspring.profiles.active=mysql -Dloader.path=./libs
> -Dalpha.server.host=0.0.0.0 -Dalpha.server.port=7080 -Dserver.port=6090
> -Dalpha.cluster.address=localhost:7080
> -D"spring.datasource.url=jdbc:mysql://localhost:3306/saga?useSSL=false=Asia/Shanghai=utf8"
> -Dspring.datasource.username=root -Dspring.datasource.password=root -jar
> alpha-server-0.4.0-exec.jar
>
> Some problems I met when I try to running alpha, I attached to the mail. Some
> configurations are not mentioned in docs, so it takes quite an effort to fix
> it.
>
> Now I meed another problem, after I changing omega from 0.3.0 to 0.4.0, I got
> following error ( demo is here:
> https://github.com/huaweicse/cse-java-chassis-samples/tree/master/HouseAppWithSpringBoot2).
>
> 2019-04-04 15:54:45.179 INFO 5668 --- [ntloop-thread-0]
> c.h.p.f.auth.credentials.AKSKManager : The application missing project
> infomation, so choose a nearest one [cn-north-1]
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'compensableAnnotationProcessor' defined in class
> path resource
> [org/apache/servicecomb/pack/omega/transaction/spring/TransactionAspectConfig.class]:
> Unsatisfied dependency expressed through method
> 'compensableAnnotationProcessor' parameter 0; nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' available: expected
> at least 1 bean which qualifies as autowire candidate. Dependency
> annotations: {}
> at
> org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:732)
> at
> org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:474)
> at
>
Re: [VOTE] Release Apache ServiceComb Java-Chassis version 1.2.0 (RC-02)
Asif, thx for taking care of it. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Apr 8, 2019 at 11:30 AM Mohammad Asif Siddiqui wrote: > > Okay, I am closing this vote, I will recut the new RC and start the vote > thread. > > Regards > Asif > > On 2019/04/08 02:04:42, wjm wjm wrote: > > yes, SCB-1240 better to be in 1.2.0. > > > > Willem Jiang 于2019年4月8日周一 上午9:59写道： > > > > > Oh,I'm sorry, it's my fault. I forgot to push the change of SCB-1240 into > > > the > > > release/1.2.0 branch in the weekend. > > > > > > Now the change is pushed into release/1.2.0 branch. Do we need to > > > consider to recut the release? > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > > > > On Mon, Apr 8, 2019 at 9:09 AM wjm wjm wrote: > > > > > > > > “Release Tag” is not correct? > > > > > > > > Mohammad Asif Siddiqui 于2019年4月6日周六 下午9:21写道： > > > > > > > > > Hello All, > > > > > > > > > > This is a call for a Vote to release Apache ServiceComb Java-Chassis > > > > > version 1.2.0 (RC-02) > > > > > > > > > > Release Notes : > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344561 > > > > > > > > > > > > > > > Release Candidate : > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/1.2.0/rc-02/ > > > > > > > > > > > > > > > Staging Repo : > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheservicecomb-1385 > > > > > > > > > > > > > > > Release Tag : > > > > > https://github.com/apache/servicecomb-java-chassis/releases/tag/1.2.0 > > > > > > > > > > Release CommitID : 8b1723e2fcd2beb86ba05be8d32d3f1b64024eb1 > > > > > > > > > > Keys to verify the Release Candidate : > > > > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > > > > > > > > > Voting will start now ( Saturday, 6th April, 2019) and will remain > > > open for > > > > > at-least 72 hours, Request all PMC members to give their vote. > > > > > > > > > > [ ] +1 Release this package as 1.2.0 > > > > > [ ] +0 No Opinion > > > > > [ ] -1 Do not release this package because > > > > > > > > > > On the behalf of ServiceComb Team > > > > > Mohammad Asif Siddiqui > > > > > > > > > >
Re: [VOTE] Release Apache ServiceComb Java-Chassis version 1.2.0 (RC-02)
Okay, I am closing this vote, I will recut the new RC and start the vote thread. Regards Asif On 2019/04/08 02:04:42, wjm wjm wrote: > yes, SCB-1240 better to be in 1.2.0. > > Willem Jiang 于2019年4月8日周一 上午9:59写道： > > > Oh,I'm sorry, it's my fault. I forgot to push the change of SCB-1240 into > > the > > release/1.2.0 branch in the weekend. > > > > Now the change is pushed into release/1.2.0 branch. Do we need to > > consider to recut the release? > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > > > On Mon, Apr 8, 2019 at 9:09 AM wjm wjm wrote: > > > > > > “Release Tag” is not correct? > > > > > > Mohammad Asif Siddiqui 于2019年4月6日周六 下午9:21写道： > > > > > > > Hello All, > > > > > > > > This is a call for a Vote to release Apache ServiceComb Java-Chassis > > > > version 1.2.0 (RC-02) > > > > > > > > Release Notes : > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344561 > > > > > > > > > > > > Release Candidate : > > > > > > > > > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/1.2.0/rc-02/ > > > > > > > > > > > > Staging Repo : > > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheservicecomb-1385 > > > > > > > > > > > > Release Tag : > > > > https://github.com/apache/servicecomb-java-chassis/releases/tag/1.2.0 > > > > > > > > Release CommitID : 8b1723e2fcd2beb86ba05be8d32d3f1b64024eb1 > > > > > > > > Keys to verify the Release Candidate : > > > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > > > > > > > Voting will start now ( Saturday, 6th April, 2019) and will remain > > open for > > > > at-least 72 hours, Request all PMC members to give their vote. > > > > > > > > [ ] +1 Release this package as 1.2.0 > > > > [ ] +0 No Opinion > > > > [ ] -1 Do not release this package because > > > > > > > > On the behalf of ServiceComb Team > > > > Mohammad Asif Siddiqui > > > > > > >
Re: [VOTE] Release Apache ServiceComb Java-Chassis version 1.2.0 (RC-02)
yes, SCB-1240 better to be in 1.2.0. Willem Jiang 于2019年4月8日周一 上午9:59写道： > Oh,I'm sorry, it's my fault. I forgot to push the change of SCB-1240 into > the > release/1.2.0 branch in the weekend. > > Now the change is pushed into release/1.2.0 branch. Do we need to > consider to recut the release? > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > On Mon, Apr 8, 2019 at 9:09 AM wjm wjm wrote: > > > > “Release Tag” is not correct? > > > > Mohammad Asif Siddiqui 于2019年4月6日周六 下午9:21写道： > > > > > Hello All, > > > > > > This is a call for a Vote to release Apache ServiceComb Java-Chassis > > > version 1.2.0 (RC-02) > > > > > > Release Notes : > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344561 > > > > > > > > > Release Candidate : > > > > > > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/1.2.0/rc-02/ > > > > > > > > > Staging Repo : > > > > > > > https://repository.apache.org/content/repositories/orgapacheservicecomb-1385 > > > > > > > > > Release Tag : > > > https://github.com/apache/servicecomb-java-chassis/releases/tag/1.2.0 > > > > > > Release CommitID : 8b1723e2fcd2beb86ba05be8d32d3f1b64024eb1 > > > > > > Keys to verify the Release Candidate : > > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > > > > > Voting will start now ( Saturday, 6th April, 2019) and will remain > open for > > > at-least 72 hours, Request all PMC members to give their vote. > > > > > > [ ] +1 Release this package as 1.2.0 > > > [ ] +0 No Opinion > > > [ ] -1 Do not release this package because > > > > > > On the behalf of ServiceComb Team > > > Mohammad Asif Siddiqui > > > >
Re: [VOTE] Release Apache ServiceComb Java-Chassis version 1.2.0 (RC-02)
Oh,I'm sorry, it's my fault. I forgot to push the change of SCB-1240 into the release/1.2.0 branch in the weekend. Now the change is pushed into release/1.2.0 branch. Do we need to consider to recut the release? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Apr 8, 2019 at 9:09 AM wjm wjm wrote: > > “Release Tag” is not correct? > > Mohammad Asif Siddiqui 于2019年4月6日周六 下午9:21写道： > > > Hello All, > > > > This is a call for a Vote to release Apache ServiceComb Java-Chassis > > version 1.2.0 (RC-02) > > > > Release Notes : > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344561 > > > > > > Release Candidate : > > > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/1.2.0/rc-02/ > > > > > > Staging Repo : > > > > https://repository.apache.org/content/repositories/orgapacheservicecomb-1385 > > > > > > Release Tag : > > https://github.com/apache/servicecomb-java-chassis/releases/tag/1.2.0 > > > > Release CommitID : 8b1723e2fcd2beb86ba05be8d32d3f1b64024eb1 > > > > Keys to verify the Release Candidate : > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > > > Voting will start now ( Saturday, 6th April, 2019) and will remain open for > > at-least 72 hours, Request all PMC members to give their vote. > > > > [ ] +1 Release this package as 1.2.0 > > [ ] +0 No Opinion > > [ ] -1 Do not release this package because > > > > On the behalf of ServiceComb Team > > Mohammad Asif Siddiqui > >
Re: [VOTE] Release Apache ServiceComb Java-Chassis version 1.2.0 (RC-02)
“Release Tag” is not correct? Mohammad Asif Siddiqui 于2019年4月6日周六 下午9:21写道： > Hello All, > > This is a call for a Vote to release Apache ServiceComb Java-Chassis > version 1.2.0 (RC-02) > > Release Notes : > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344561 > > > Release Candidate : > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/1.2.0/rc-02/ > > > Staging Repo : > > https://repository.apache.org/content/repositories/orgapacheservicecomb-1385 > > > Release Tag : > https://github.com/apache/servicecomb-java-chassis/releases/tag/1.2.0 > > Release CommitID : 8b1723e2fcd2beb86ba05be8d32d3f1b64024eb1 > > Keys to verify the Release Candidate : > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > Voting will start now ( Saturday, 6th April, 2019) and will remain open for > at-least 72 hours, Request all PMC members to give their vote. > > [ ] +1 Release this package as 1.2.0 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui >
Re: [PROPOSAL] ServiceComb MetaConfig
I prefer rokie. "kie" has same pronouce with key and "ro" means rollable, although rollable is not the most attractive feature of this service, but this rokie sounds like a name Willem Jiang 于2019年4月5日周五 下午10:59写道： > I think we could create a new repo for creating a prototype this > meta-data management project. > Now we just need to decide the name of the repo. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Mar 29, 2019 at 12:16 PM Xiaoliang Tian > wrote: > > > > maybe the name confused，it is a service only for configurations，but > > the key contains metadata > > key1: log_level(service=cart, version=1.0, app=mall) > > key2: log_level(service=cart, version=1.0, app=mall, ip=x.x.x.x) > > that is 2 different keys > > > > you can consider apollo has fixed metadata and one fixed view to math > their > > own scenario. > > > > but in apollo, key can be very complicated, user can not easily observe > > keys, a lot of metadata will be attacted to key name, just like ip to > > "log_level" > > > > Willem Jiang 于2019年3月29日周五 上午11:36写道： > > > > > Hi Xiaoliang, > > > > > > Do you propose we start a new project to manage the micro services meta > > > datas? > > > Currently we just have a solution to integrate with with Apollo for > > > configuration management, but what's the difference between the > > > service metadata and configuration? > > > I could help us to understand the proposal, if we can drop a clear line > > > for it. > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Fri, Mar 29, 2019 at 10:52 AM Xiaoliang Tian > > > wrote: > > > > > > > > MetaConfig is a service for configuration management in an large > scaled > > > > distrbuted system. > > > > > > > > Currently we use ctrip appllo for config managment, but it is build > for a > > > > paticular scenario. it has fixed schema > application,environment,cluster > > > and > > > > namespace. Each key belong to that schema. > > > > > > > > But it is not enough for operator to manage a complicated > infrasctructure > > > > or application cluster. > > > > > > > > So here is the proposal to build a brand new config management > service, > > > > > > > > *Features: * > > > > *key with rich metadata: *user can define metadata for a key , that > > > > distinguish from key to another key. a key will not be stringed by > fixed > > > > schema. metadata is like "env=test, service=cart, version=1.0" or > > > > "cluster=xxx" or "env=test, service=cart, version=1.0, ip=x.x.x.x" > > > > *validator: *value can be checked by user defined python script, so > in > > > > runtine if someone want to change this value, the script will check > if > > > this > > > > value is properate. > > > > *encryption webhook: *. value can by ecrypt by your custom encryption > > > > service. > > > > *event producer: *producer will send key changes event to a target > > > > service(kafka,rabbitmq, customed). > > > > *config view: *by setting metadata criteria, MetaConfig will > aggregate a > > > > view to return all key values which match those metadata, so that > > > operator > > > > can mange key in their own understading to a distributed system in > > > > seperated views. > > > > *config batch action: * with metadate, you can batch update, delete > key > > > > values. for example: update all "service=cart version=1.0" > configuration > > > > log level to "DEBUG" or just update "service=cart version=1.0, > > > ip=x.x.x.x" > > > > . > > > > *rich value type: *not ony plain text any more, but support to be > aware > > > of > > > > ini, json,yaml,xml and java properties > > > > *heterogenous configuration system: *able to manage configuration in > k8s > > > > and consul or even more, you can update, delete, and use config view > for > > > > those systems, and you can integrate with your own config system to > > > > MetaConfig by following standardized API and model > > > >
