jk1
Support scanning of buildScripts / used gradle plugins
In our project, we need to scan also the build-time dependencies for licenses. In gradle they can be access via project.buildScript.
For this, the buildScriptProjects configuration option was introduced. It respects all other configuration like 'configurations'.
The implementation is utilizing the existing ProjectReader for this because the required fields (configurations and dependencies) can also be found in ScriptHandler. There is only a change required: to use a general data structure for accessing these fields.
@chadlwilson / @bdellegrazie / @jk1 what do you think about the PR? We use it in our project already for some time.
If there is interest, I can rebase it.
Hi @balrok!
This is rather unusual to track build script dependencies since they are not shipped or otherwise used in production. Yet is see no problem in incorporating this into the upstream. If you could rebase it, it would be great.
Rebased and also added a commit: https://github.com/balrok/Gradle-License-Report/commit/0532295c64e080214519d2e6163df89ae6824e9f
Reason it is needed: we have several plugins creating code for us. Also we want to better be safe than sorry