Hey guys,
I need some feedback about the name of the new dependency report that
shows "the usages of each dependency". For more information about the
report, including mock-ups, see:
https://github.com/gradle/gradle/blob/master/design-docs/dependency-resolution-reporting.md#new-report-shows-usages-of-each-dependency
Currently, the report is called "dependencyInsight". That was the
first name that I came up with, I'm not particularly happy with it. It
suppose to convey that we're 'zooming' into a particular dependency VS
showing all. Therefore it the codebase in master, you can already find
a task named "depednecyInsight" of type: DependencyInsightReportTask.
There's a already some basic command-line support for this report in
the master.
1. We should come up with reasonable name for the report before 1.3
and also for the command line options that come with this report. The
way one can use the report from the command line (current state of
things on master):
gradle dependencyInsight --include 'com.org:foo' --configuration 'runtime'
Some other ideas:
gradle dependencyUsages --of 'com.org:foo' --configuration 'runtime'
gradle dependents --of 'com.org:foo' --configuration 'runtime'
gradle whichDependency --include 'com.org:foo' --configuration 'runtime'
gradle showDependency --include 'com.org:foo' --configuration 'runtime'
gradle dependency --show 'com.org:foo' --configuration 'runtime'
2. Should we make the new report available by default, e.g. as the
implicit tasks are at the moment?
This would improve the discoverability of the feature before we
implement the auto-apply plugins/tasks. There's a slight downside: say
we use a different name than 'dependencies' for the task name (which
is very likely because it is a different report). Then the new name
may clash with a task name already existing in the client build.
Cheers!
--
Szczepan Faber
Principal engineer@gradleware
Lead@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
