Skip to content

Conversation

@merlimat
Copy link
Contributor

@merlimat merlimat commented Nov 5, 2018

Motivation

@merlimat merlimat added this to the 4.9.0 milestone Nov 5, 2018
@merlimat merlimat self-assigned this Nov 5, 2018
</dependency>
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-codec-socks</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is already being pulled by other dependencies (eg: finagle, etc..). Here, I'm not adding a new dependency, just pinning all the artifacts to be on the same version.

</dependency>
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-handler-proxy</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above

@sijie
Copy link
Member

sijie commented Nov 6, 2018

run integration tests

Copy link
Contributor

@ivankelly ivankelly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, one question about the transports

- lib/io.netty-netty-handler-proxy-4.1.31.Final.jar
- lib/io.netty-netty-resolver-4.1.31.Final.jar
- lib/io.netty-netty-resolver-dns-4.1.31.Final.jar
- lib/io.netty-netty-tcnative-boringssl-static-2.0.19.Final.jar
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this packaged as part of -all? I seem to recall transports were separate projects.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That one (the static ssl lib) is not part of -all

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

netty-tcnative-boringssl-static was already included as a dependency. I have upgrade from 2.0.7.Final to 2.0.19.Final since it's needed by the new Netty version

@merlimat
Copy link
Contributor Author

merlimat commented Nov 6, 2018

run integration tests

@merlimat
Copy link
Contributor Author

merlimat commented Nov 6, 2018

@eolivelli can you please check again?

Copy link
Contributor

@eolivelli eolivelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#shipit

I am preparing 4.8.1.
Do you want to cherry pick?

@merlimat
Copy link
Contributor Author

merlimat commented Nov 6, 2018

@eolivelli I think it's good to keep it for 4.9.0. The dependency change (from all to individuals) might surprise users in a patch release.

Also, there's no specific bug that was fixed in Netty-4.1.31 that we need to make available.

@eolivelli
Copy link
Contributor

@merlimat okay.
btw (Probably) I will be running soon bk 4.8.1 + latest netty version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants