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
Hi. I have a project which has a main build.gradle, and 3 sub-projects. We use the parent project to define versions for the sub-projects. It looks something like this:
When we run the plugin, it detects that both spring boot and my-library needs to be updated. It clearly prints which version updates are needed, but ultimately only the springBootVersion line in the parent is updated. If we use the versions directly in the sub-projects, the other libraries are also correctly updated. It's clear that the update mechanism works, and that it can read the correct version from the repository etc, but it just isn't updating the versions in the parent. Any thoughts on why this might be?
It doesn't seem to be the case that it's only our internal libraries, either. Spring-boot updates, but hibernate does not. It's very weird.
The text was updated successfully, but these errors were encountered:
Hi. I have a project which has a main build.gradle, and 3 sub-projects. We use the parent project to define versions for the sub-projects. It looks something like this:
In each sub-project, we reference these versions like this:
When we run the plugin, it detects that both spring boot and my-library needs to be updated. It clearly prints which version updates are needed, but ultimately only the
springBootVersion
line in the parent is updated. If we use the versions directly in the sub-projects, the other libraries are also correctly updated. It's clear that the update mechanism works, and that it can read the correct version from the repository etc, but it just isn't updating the versions in the parent. Any thoughts on why this might be?It doesn't seem to be the case that it's only our internal libraries, either. Spring-boot updates, but hibernate does not. It's very weird.
The text was updated successfully, but these errors were encountered: