Maybe we can add some lines in the release note to let the user know these warning messages are quit important when upgrading the java-chassis version. It's always good to write some upgrade documents to fill the information gap.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jan 25, 2019 at 4:57 PM wjm wjm <zzz...@gmail.com> wrote: > > sometimes, it just a warning, not fatal > > Willem Jiang <willem.ji...@gmail.com> 于2019年1月25日周五 下午4:53写道： > > > If you want user to take a good look of the warning log, you can just > > abort the boot process by default. > > Just my 2 cents. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Fri, Jan 25, 2019 at 4:43 PM wjm wjm <zzz...@gmail.com> wrote: > > > > > > currently, when we find something not so good during boot, we will print > > > log immediately > > > eg: > > > > > > - use deprecated configuration > > > - port listen failed > > > - ...... > > > > > > most developers will not notice these important messages > > > > > > so maybe we can keep current implementation > > > and collect all the information, print them after boot > > > maybe like: > > > *************** important message *************** > > > warning: > > > 1.servicecomb.rest.client.thread-count is ambiguous, suggest to use > > > servicecomb.rest.client.verticle-count. > > > error: > > > 1....... > >
