Hi Willem,
This is not an issue, this is more like a suggestion to handle the
configuration in a better way, as the values of SC_IP can still be changed in
js file as per our Readme.
So IMO we don't need to add this in Known Issues list.
Anyhow I have created a JIRA for this [1] to
Hi Asif,
Please create a JIRA for checking the apiList.js issue.
Then we can add this known issue to the release note and address it in m2
release.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On
Thanks YangBo and Cuiyihua for the suggestion.
We will move the frontend configurations to the app.conf and add the frontend
starting guide in the main Readme, so from here on there will be only 1 Readme
and 1 conf which can be used by both frontend and service-center.
Coming back to
e_0...@qq.com>
wrote:
ISSUE link: https://issues.apache.org/jira/browse/SCB-343
-- 原始邮件 --
发件人: "Sure"<sure_0...@qq.com>;
发送时间: 2018年2月12日(星期一) 下午5:27
收件人: "dev@servicecomb.apache.org"<dev@servicecomb.apache.org>;
主题: 回复: [VO
+1
Build success from source on linux/windows machine ,Basic user cases passed.
-Original Message-
From: Sure [mailto:sure_0...@qq.com]
Sent: 09 February 2018 11:40
To: dev <dev@servicecomb.apache.org>; dev@servicecomb.apache.org
Subject: 回复:[VOTE] Release Apache ServiceComb S