Closed qwert2603 closed 1 year ago
Ahh, thanks. I'll take a look at this. The link you sent to the source code is helpful. At first glance it seems like it shouldn't be hard coded like that. I'll check.
We're heavily using the list
format of dependencies and not the tree
currently, so didn't see this.
Will report back. Thanks!
Also, are you using this on anything open source? I'd love to point to a few projects that are using dependency-guard
.
Ahh, so there are 2 usages of this method.
build environment tree
project environment tree
I must have just been testing the message for the build environment. Good catch!
0.3.2 is publishing and contains this fix.
Thanks for the fix!
Also, are you using this on anything open source?
Currently not. But I may try it on some of my pet projects later.
Thank you. Are you using the library for something private or at work? Just curious what kind of configuration you have. Cheers
I'm planning to use the library for a pet project and work android-project. I also think that list
configuration is more useful than tree
. And it's helpful to guard releaseRuntimeClasspath
, debugUnitTestRuntimeClasspath
and debugAndroidTestRuntimeClasspath
for the app module and classpath
confuguration for the root gradle project to get the full picture of project dependencies.
Hello!
When
DependencyGuardTreeDiffer
writes a tree baseline file, it prints the following message (sources):But
DependencyGuardTreeDiffer
writes a tree baseline file for the givenproject.path
andconfigurationName
, not only for:
andclasspath
. So it would be useful to print the correctproject.path
andconfigurationName
in the output message.Expected example of the output message: