[ 
https://issues.apache.org/jira/browse/SCB-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528639#comment-16528639
 ] 

ASF GitHub Bot commented on SCB-671:
------------------------------------

coveralls commented on issue #787: [SCB-671]duplicate cse to servicecomb
URL: 
https://github.com/apache/incubator-servicecomb-java-chassis/pull/787#issuecomment-401529693
 
 
   
   [![Coverage 
Status](https://coveralls.io/builds/17771258/badge)](https://coveralls.io/builds/17771258)
   
   Coverage decreased (-0.03%) to 87.118% when pulling 
**720391d01f1ef1cfac19aad29687312556612a9c on liubao68:cse_servicecomb** into 
**82d47669ae2486bbd259567b7995cd27dd72061a on apache:master**.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Duplicate cse.xxx to servicecomb.xxx to work better in future
> -------------------------------------------------------------
>
>                 Key: SCB-671
>                 URL: https://issues.apache.org/jira/browse/SCB-671
>             Project: Apache ServiceComb
>          Issue Type: Improvement
>          Components: Java-Chassis
>            Reporter: liubao
>            Assignee: liubao
>            Priority: Major
>             Fix For: Java-chassis-1.0.0
>
>
> As discussed in 
> [DISCUSSION] How to migrate configurations from cse toservicecomb prefix
> It's better to map cse to servicecomb, not servicecomb to cse. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to