Zongle Wang
Zongle Wang
You can use the generated JSON file and parse info to show license page like https://github.com/chrisbanes/tivi/issues/1471.
> There is an easy way to bundle the `artifacts.json` for you, see https://github.com/cashapp/licensee/releases/tag/1.13.0. _Originally posted by @Goooler in [#206](https://github.com/google/play-services-plugins/issues/206#issuecomment-2742441753)_
Merged in #4818.
Oooops, I forgot that. Done!
Related to - https://github.com/vanniktech/gradle-maven-publish-plugin/issues/954 - #330 - #377
License models are easily accessed from https://github.com/cashapp/licensee/releases/tag/1.13.0
See #429.
And we can publish snapshots on main branch, users can try out them as a workaround. I did this on https://github.com/GradleUp/shadow/blob/5bcdb171394bb42adad80b6acd650bb71eafeeff/.github/workflows/ci.yml#L27-L44
We should get rid of using jitpack. We are using `io.github.gradle-nexus.publish-plugin` to publish maven artifacts to MavenCentral, MavenCentral's snapshots also support snapshot Gradle plugins. I'll send a PR later. https://github.com/diffplug/spotless/blob/4552da0f3535e0ac74ffe3ec7f3e813621c5d023/gradle/java-publish.gradle#L19-L29
There are few thing to do: - Get rid of jitpack. - Would prefer [com.vanniktech.maven.publish](https://github.com/vanniktech/gradle-maven-publish-plugin) over `io.github.gradle-nexus.publish-plugin`, I tried to migrate this but there are so many complex logic should...