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

Do not depend on generated classes for update-secret extension #627

Conversation

acogoluegnes
Copy link
Contributor

Some CI testing jobs are using the 3.7 branch of codegen, which does not contain
the update-secret extension. The Java client then cannot be built
because it requires some generated code for the extension.

This commit adds the code to handle update-secret and thus
makes the generated code not necessary. This is just a workaround for
these testing jobs to succeed, it does not change the handling of the
update-secret extension in the client.

[#167029587]

References #626

Some CI testing jobs are using the 3.7 branch of codegen, which does not contain
the update-secret extension. The Java client then cannot be built
because it requires some generated code for the extension.

This commit adds the code to handle update-secret and thus
makes the generated code not necessary. This is just a workaround for
these testing jobs to succeed, it does not change the handling of the
update-secret extension in the client.

[#167029587]

References #626
@acogoluegnes acogoluegnes added this to the 5.8.0 milestone Sep 16, 2019
@michaelklishin michaelklishin merged commit 6c34023 into master Sep 16, 2019
@michaelklishin
Copy link
Member

I'm not sure about the precedent this is setting. We could simply update the v3.7.x pipeline. But this is an acceptable solution. Thanks for the quick turnaround.

@michaelklishin michaelklishin deleted the rabbitmq-java-client-classes-for-update-secret-extension branch September 16, 2019 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants