Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Gradle multi-module projects. #301

Closed
CristianGM opened this issue Aug 27, 2020 · 2 comments
Closed

Add support for Gradle multi-module projects. #301

CristianGM opened this issue Aug 27, 2020 · 2 comments

Comments

@CristianGM
Copy link

The approach to inject the plugin dependency-license-report plugin used here is making a modified copy of the build.gradle and running it with -b, it means Gradle will ignore the settings.gradle and ignore all the subprojects (modules).

I asked on Gradle Slack and they told me to use an init script instead so it works properly, that will also fix the issue that we are only considering build.gradle and not the "new" build.gradle.kts which would change the syntax slightly.

Alternatively it would be possible to copy the settings.gradle to another file adding to it rootProject.buildFileName = "license-....gradle"´ and using it adding to the cli -c licensed-settings.gradle, but then we still need to add support for .gradle.kts files

@jonabc
Copy link
Contributor

jonabc commented Aug 27, 2020

@CristianGM I don't have deep knowledge of Gradle, but am happy with any changes that maintain backwards compatibility while solving the problems you mention. Would you be able to open a PR?

@jonabc
Copy link
Contributor

jonabc commented Jan 5, 2023

This was resolved with #583, which will be part of the major version 4.0 release

@jonabc jonabc closed this as completed Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants