-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-module Gradle doesn't resolve properties set in parent build file #1086
Comments
I am not really sure how much we can do about it, given that purposefully we avoid bring in build tool dependencies and we are parsing files ourselves. The only possible solution I could think of is navigating the directory hierarchy from module root to project root and try to detect global settings. |
Is this not what is done for maven? |
No, AFAIR for maven the version is read from the parent element. |
@iocanel There's any easy fix for this. Require that users define the version in Currently the code is only looking in the current project directory, but for multi-module project it needs to search up until the root project directory. The best solution would gather all the |
In a multi-module Gradle project with properties (e.g. version) set for all projects in the root
build.gradle.kts
, dekorate doesn't resolve those properties and emits a warning.Example
/build.gradle.kts
:This will emit the warning
Could not detect project version. Using 'latest'.
.The text was updated successfully, but these errors were encountered: