You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a concrete reason for always only having the latest version of the library published on maven central?
Removing the old version after the new one has been published frequently breaks compilation and forces us to update the dependency declaration.
This is no big issue for apps, but as we use the library in an sdk, we need to include the webrtc-sdk as aar, to avoid having to release new library versions when the old webrtc-sdk version cannot be resolved anymore.
The text was updated successfully, but these errors were encountered:
Is there a concrete reason for always only having the latest version of the library published on maven central?
Removing the old version after the new one has been published frequently breaks compilation and forces us to update the dependency declaration.
This is no big issue for apps, but as we use the library in an sdk, we need to include the
webrtc-sdk
as aar, to avoid having to release new library versions when the oldwebrtc-sdk
version cannot be resolved anymore.The text was updated successfully, but these errors were encountered: