The feature `start.sh -v` doesn't wrok

[wsm12138]

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

• Searched open and closed GitHub issues.
• Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

1537e47487afd29071aa72a742c2d1701d348aaa

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-Proxy

Expected behavior

the build time should be correct

Actual behavior

### Reason analyze (If you can)

maybe Git-Commit-Id-Plugin doesn't work?

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

git clone shardingsphere cd shardingsphere git checkout 1537e47487afd29071aa72a742c2d1701d348aaa ./mvnw clean install -Prelease -T1C -DskipTests -Djacoco.skip=true -Dcheckstyle.skip=true -Drat.skip=true -Dmaven.javadoc.skip=true -B tar -xf apache*.tar.gz ./bin/start.sh -v

[kimmking]

The error message is clearly.

[wsm12138]

The error message is clearly.

I think it just a warning,not error.

beside Resolved warnings it still show incorrect Build time: 2022-12-12T03:18:10+0800

[wsm12138]

@strongduanmu @RaigorJiang Hi,can we have a look? if convenient.