https://github.com/jjohannes/what-if-gradle-metadata

What if... Gradle Module Metadata would have existed when your favorite JVM library was published
https://github.com/jjohannes/what-if-gradle-metadata

Last synced: 3 days ago
JSON representation

What if... Gradle Module Metadata would have existed when your favorite JVM library was published

• Host: GitHub
• URL: https://github.com/jjohannes/what-if-gradle-metadata
• Owner: jjohannes
• Created: 2019-10-02T19:32:44.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2019-11-06T16:32:32.000Z (about 5 years ago)
• Last Synced: 2025-01-08T20:40:50.839Z (3 days ago)
• Language: Kotlin
• Size: 108 KB
• Stars: 3
• Watchers: 5
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.MD

Awesome Lists containing this project

README

        
# What if...

...Gradle Module Metadata would have existed when your favorite JVM library was published .

A demonstration of how Gradle Module Metadata could look like for a number of famous open-source JVM libraries.

## How to use?

- Clone this repository

- Run [publish.sh](publish.sh) to fill the *repository* folder with versions of libraries with Gradle Module Metadata added.

  The artifacts (jars) are the original artifacts taken from Maven Central.

  You can inspect the [libraries](libraries) folder that contains the Gradle builds re-defining dependencies and other properties of the libraries to generate the metadata.

- Go into the [usecases](usecases) folder and inspect the Gradle builds in there to see how different issues are now solved.  

- To see the resulting classpath (or conflict) run `./gradlew ::checkClasspath` or  `./gradlew ::dependencise` inside the [usecases](usecases) folder.

  You can also run with the `--scan` option to inspect the dependencies in a [build scan](https://gradle.com/build-scans/).