Closed sdoward closed 7 months ago
This is one of the intended use of the library. I don't think the right path is configuring our tasks, but either doing one of two things:
The functionality for registering an asset-generating task is relatively new and I have not experimented with it yet: https://issuetracker.google.com/issues/37085092#comment4
You can easily just consume the json file using standard Gradle api:
val myCustomTask = tasks.register("myCustomTask", MyCustomTask::class) {
val licenseeJsonFile: Provider<RegularFile> = tasks.licensee.flatMap { it.outputDir.file("artifacts.json") }
myInputFile.set(licenseeJsonFile)
}
But we could also expose the file as a task property:
val myCustomTask = tasks.register("myCustomTask", MyCustomTask::class) {
val licenseeJsonFile: Provider<RegularFile> = tasks.licensee.flatMap { it.artifactsJsonFile }
myInputFile.set(licenseeJsonFile)
}
As an android developer I want to be able to configure the location of the artefacts.json file So that I can bundle it in my app as part of the
./assets
directoryWe use the .json file to create a screen that shows the licences to our users. It would be nice if we can easily add that file as part of the build/ci pipeline.