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

Ship downstream dependencies of msal4j with updated versions #880

Open
billwert opened this issue Nov 21, 2024 · 0 comments
Open

Ship downstream dependencies of msal4j with updated versions #880

billwert opened this issue Nov 21, 2024 · 0 comments
Labels
AzureSDK Issues and requests affecting the Azure SDK Fundamentals For issues focused on Java best practices, industry standards, etc. SDK-Consistency Items that deal with consistency between all MSALs

Comments

@billwert
Copy link

Ref customer issue: Azure/azure-sdk-for-java#42942

In short, dependencies of msal4j should re-ship whenever msal4j ships with updated version numbers to avoid potential dependency resolution conflicts, etc. I think this includes persistence as well as broker.

Ideally all dependencies will be aligned between these packages, so include things like slf4j.

@Avery-Dunn Avery-Dunn added SDK-Consistency Items that deal with consistency between all MSALs AzureSDK Issues and requests affecting the Azure SDK Fundamentals For issues focused on Java best practices, industry standards, etc. labels Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AzureSDK Issues and requests affecting the Azure SDK Fundamentals For issues focused on Java best practices, industry standards, etc. SDK-Consistency Items that deal with consistency between all MSALs
Projects
None yet
Development

No branches or pull requests

2 participants