Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix netty-all artifact #11274

Merged
merged 1 commit into from May 19, 2021
Merged

Fix netty-all artifact #11274

merged 1 commit into from May 19, 2021

Conversation

normanmaurer
Copy link
Member

Motivation:

612ab58 did change the way how netty-all was produced by unfortunally it messed up the dependency graph for our native artifacts. This commit reverts changes done by 612ab58 and also clean up the profiles

Modifications:

netty-all is useable again

Result:

Fixes #11272

Motivation:

612ab58 did change the way how netty-all was produced by unfortunally it messed up the dependency graph for our native artifacts. This commit reverts changes done by 612ab58 and also clean up the profiles

Modifications:

netty-all is useable again

Result:

Fixes #11272
@normanmaurer normanmaurer added this to the 4.1.65.Final milestone May 18, 2021
</dependency>
</dependencies>
</profile>

<profile>
<id>full</id>
Copy link
Member Author

Choose a reason for hiding this comment

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

This is not needed anymore as we moved the Javadoc etc generated to the parent pom.xml

@normanmaurer
Copy link
Member Author

/cc @fredericBregier

@fredericBregier
Copy link
Member

@normanmaurer OK, I will wait for a new release to be able to check, I think it shall be ok. Thanks !

Copy link
Contributor

@chrisvest chrisvest left a comment

Choose a reason for hiding this comment

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

I guess this reopens #4671

@normanmaurer
Copy link
Member Author

@chrisvest sadly yes :/

@normanmaurer
Copy link
Member Author

/cc @candrews

@candrews
Copy link
Contributor

Instead of reverting, I feel like fixing the problem would be preferable. I'll take a look - I see others are doing so as well

@normanmaurer
Copy link
Member Author

@candrews generally speaking yes... that said I think we need to release a regression fix release asap. And as it has shown we need to take more time to really ensure that everything works as expected.

@chrisvest
Copy link
Contributor

I agree with @normanmaurer. Since this turned out to be unexpectedly tricky, and there are other fixes waiting for release, I think it's a better trade-off to do the revert in this PR, regressing the netty-all class path behaviour to the state it's been for years prior, and then there's no time pressure on #11278.

@normanmaurer
Copy link
Member Author

Let's pull this in and then #11278 can revert this change and add its own changes on top of it.

@normanmaurer normanmaurer merged commit 037eddd into 4.1 May 19, 2021
@normanmaurer normanmaurer deleted the all_fix branch May 19, 2021 09:12
normanmaurer added a commit that referenced this pull request May 19, 2021
Motivation:

612ab58 did change the way how netty-all was produced by unfortunally it messed up the dependency graph for our native artifacts. This commit reverts changes done by 612ab58 and also clean up the profiles

Modifications:

netty-all is useable again

Result:

Fixes #11272
raidyue pushed a commit to raidyue/netty that referenced this pull request Jul 8, 2022
Motivation:

612ab58 did change the way how netty-all was produced by unfortunally it messed up the dependency graph for our native artifacts. This commit reverts changes done by 612ab58 and also clean up the profiles

Modifications:

netty-all is useable again

Result:

Fixes netty#11272
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.

netty-all 4.1.64 has a broken dependency graph
4 participants