The gradle-versioneye-plugin can't resolve our dynmic variables automatically from the root project
Closed this issue · 6 comments
the gradle-versioneye-plugin can't resolve our dynmic variables automatically from the root project
as in $rootProject.googlePlayServices
compile "com.google.firebase:firebase-core:$rootProject.googlePlayServices"
we are using version 1.4
configuration in root project
versioneye { includeSubProjects = true exclude configurations.findAll { !it.canBeResolved }*.name as String[] }
What's the output of gradle dependencies?
`1: Task failed with an exception.
- What went wrong:
Execution failed for task ':rosie-aia:versioneye-pom'.
Resolving configuration 'api' directly is not allowed
- Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.
==============================================================================
2: Task failed with an exception.
- What went wrong:
Execution failed for task ':versioneye-pom'.
Resolving configuration 'api' directly is not allowed
- Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.
==============================================================================
3: Task failed with an exception.
- What went wrong:
Execution failed for task ':rosie-app:versioneye-pom'.
Resolving configuration 'androidTestAnnotationProcessor' directly is not allowed
- Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.
==============================================================================
4: Task failed with an exception.
- What went wrong:
Execution failed for task ':rosie-lib:versioneye-pom'.
Resolving configuration 'androidTestAnnotationProcessor' directly is not allowed
From the output looks like this is the same problem a in #34.
Can you try again with the current snapshot?
The reason why it fails even if the workaround is used is most likely that subprojects are included and there are configurations that are not resolvable that don't occur in the main project.
Fix for issue with resolving configurations contained in 1.5.0 release. From the initial report it is not clear if this is the only problem here. Please reopen if the issue persists.