Currently Pride uses the gradle.projectsEvaluated { ... } hook to actually create the dynamic dependencies as Gradle dependencies. This is because project group names not evaluated before this point. However, if we stored the group names in a file during pride init, we could use that instead, and so we could create dependencies straight away.
lptr
commented
10 years ago
Currently Pride uses the
gradle.projectsEvaluated { ... }hook to actually create the dynamic dependencies as Gradle dependencies. This is because project group names not evaluated before this point. However, if we stored the group names in a file during pride init, we could use that instead, and so we could create dependencies straight away.