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
To define versions, there are currently two documented methods:
Use a platform (either as spearate project or as variant of an application project)
Use Gradle's version catalog ([versions] section)
From usability (2) is a bit nicer because it just requires you to add a file. (1) requires a more involved setup and versions are "hidden" in a build.gradle file. But (1) has the big advantage that all versions are always used automatically and allows you to influence the versions of transitive dependencies for which you never have a direct require.
I think in the context of this plugin, it would be nice to have another option with a similar usability as (2) but the effect of (1). A solution could be to have the versions in a dedicated properties file (with module.name=version entries) that the plugins than translated into version constraints for all modules of your project.
The text was updated successfully, but these errors were encountered:
- In more cases, a platform is the appropriate solution to also
influence versions of transitive dependencies
- We might add the option to use a properties file (#68) which
makes it even more unclear if versions are expected in the catalog
or not
jjohannes
changed the title
Properties file for module versions
[Maybe] Properties file for module versions
Nov 24, 2023
To define versions, there are currently two documented methods:
[versions]
section)From usability (2) is a bit nicer because it just requires you to add a file. (1) requires a more involved setup and versions are "hidden" in a
build.gradle
file. But (1) has the big advantage that all versions are always used automatically and allows you to influence the versions of transitive dependencies for which you never have a directrequire
.I think in the context of this plugin, it would be nice to have another option with a similar usability as (2) but the effect of (1). A solution could be to have the versions in a dedicated properties file (with
module.name=version
entries) that the plugins than translated into version constraints for all modules of your project.The text was updated successfully, but these errors were encountered: