DInTheName edited a comment on issue #2497:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2497#issuecomment-894929451
**Dependency Tree is :**
[INFO] | +- org.apache.servicecomb:deployment:jar:2.0.2:compile
[INFO] | +- org.apache.servicecomb:foundation-vertx:jar:2.0.2:compile
[INFO] | | +- io.vertx:vertx-core:jar:3.9.4:compile
[INFO] | | | \- io.netty:netty-resolver-dns:jar:4.1.63.Final:compile
[INFO] | | | \- io.netty:netty-codec-dns:jar:4.1.63.Final:compile
[INFO] | | +- io.vertx:vertx-web:jar:3.9.4:compile
[INFO] | | | +- io.vertx:vertx-web-common:jar:3.9.4:compile
[INFO] | | | +- io.vertx:vertx-auth-common:jar:3.9.4:compile
[INFO] | | | \- io.vertx:vertx-bridge-common:jar:3.9.4:compile
[INFO] | | \- org.apache.servicecomb:foundation-ssl:jar:2.0.2:compile
[INFO] | | \-
io.netty:netty-tcnative-boringssl-static:jar:2.0.29.Final:compile
[INFO] | +- org.apache.servicecomb:foundation-config:jar:2.0.2:compile
[INFO] | | +- commons-configuration:commons-configuration:jar:1.10:compile
[INFO] | | +- org.yaml:snakeyaml:jar:1.26:compile
[INFO] | | +- io.netty:netty-codec:jar:4.1.63.Final:compile
[INFO] | | +- io.netty:netty-codec-http:jar:4.1.63.Final:compile
[INFO] | | +- io.netty:netty-codec-http2:jar:4.1.63.Final:compile
[INFO] | | +- io.netty:netty-common:jar:4.1.63.Final:compile
[INFO] | | +- io.netty:netty-handler:jar:4.1.63.Final:compile
[INFO] | | +- io.netty:netty-buffer:jar:4.1.63.Final:compile
[INFO] | | +- io.netty:netty-codec-socks:jar:4.1.63.Final:compile
[INFO] | | +- io.netty:netty-handler-proxy:jar:4.1.63.Final:compile
[INFO] | | +- io.netty:netty-resolver:jar:4.1.63.Final:compile
[INFO] | | \- io.netty:netty-transport:jar:4.1.63.Final:compile
This versions can match?
i want to use java-chassis-spring-boot-starter-2.0.2.jar, What Is the
Mapping Between Netty and Java-Chassis Versions?
Which version does Netty choose?
Pls，Thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
