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
Now that we have more and more essential extensions such as URID, we should provide a way for plugin developers to not care much about the "missing" extensions.
In Gradle Maven package resolution system there is a concept called BOM (bill of material) that works like a catalog set of specific versions of dependencies. The most known one is Jetpack Compose BOM, but there are other BOMs as well (such as ktor BOM).
We could define a standard set of those, described in aap_metadata.xml so that we do not have to deal with it for every plugin, every time we add another essential extension.
The text was updated successfully, but these errors were encountered:
Now that we have more and more essential extensions such as URID, we should provide a way for plugin developers to not care much about the "missing" extensions.
In Gradle Maven package resolution system there is a concept called BOM (bill of material) that works like a catalog set of specific versions of dependencies. The most known one is Jetpack Compose BOM, but there are other BOMs as well (such as ktor BOM).
We could define a standard set of those, described in
aap_metadata.xml
so that we do not have to deal with it for every plugin, every time we add another essential extension.The text was updated successfully, but these errors were encountered: