dependencyLock.configurationNames and custom configurations.

[ftclausen]

Has anyone encountered an issue when using a custom dependency configuration in dependencyLock.configurationNames? This causes (for us) an issue with Ivy metadata in Gradle. For example projectA depends on projectB and projectB is in the "myConfiguration" configuration container. This results in the following :

Caused by: java.lang.RuntimeException: Module version com.example:projectA:1.0.0, configuration 
'detachedConfiguration1' declares a dependency on configuration 'myConfiguration' which is not 
declared in the module descriptor for com.example:projectB:2.0.0

where the detachedConfiguration1 is created by gradle-dependency-lock-plugin as part of GenerateLockTask.groovy; specifically when resolution is triggered over here. I'm not sure why it is a detached configuration since we are iterating over attached (and named) configurations. Look at the cached ivy.xml for projectB there is indeed no myConfiguration listed.

[ftclausen]

I found a solution to this in the way we declare our dependencies in our build; I'll close this issue.