Ship downstream dependencies of msal4j with updated versions #880
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
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.
The text was updated successfully, but these errors were encountered: