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

Ship the GraalVM metadata repository as an artifact alongside NBT #331

Merged
merged 7 commits into from
Oct 12, 2022

Commits on Oct 10, 2022

  1. Bump the metadata repository version

    This also moves the constant to the `libs.versions.toml` file so that it
    is both easier to upgrade *and* available in build scripts without having
    to parse source files. This is going to be useful for repackaging the
    repository.
    melix committed Oct 10, 2022
    Configuration menu
    Copy the full SHA
    f303996 View commit details
    Browse the repository at this point in the history

Commits on Oct 11, 2022

  1. Download the metadata repository as a publishable artifact

    This commit introduces a task which is responsible for downloading the
    current metadata repository version and bundle it as a publishable artifact.
    This means that the ZIP file of the metadata repository is going to be
    downloaded from the GraalVM metadata repository, and published as a
    _classified_ artifact on the `graalvm-reachability-metadata` module.
    
    It is possible to check the result by calling:
    
        ./gradlew graalvm-reachability-metadata:pAPTCR
    
    and checking the contents of the `build/common-repo` directory. A file
    named `graalvm-reachability-metadata-<nbt version>-repository.zip` file
    should be visible.
    
    This will make it possible to consume the metadata repository as a Maven
    artifact.
    melix committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    1d60187 View commit details
    Browse the repository at this point in the history
  2. Make the Gradle plugin use the metadata repository from Maven

    This commit makes it so that if the user doesn't specify any URL for the
    repository, nor any specific version, then we would use the repository
    artifact which is bundled with the NBT release on Maven Central (or
    any repository configured in the build). This makes it possible to
    use the Gradle native build tools exclusively with Maven repositories.
    melix committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    06405b5 View commit details
    Browse the repository at this point in the history
  3. Make the Maven plugin use the metadata repository from Maven Central

    Similarly to the Gradle plugin, this commit makes it so that if the user
    doesn't specify any URL for the repository, nor any specific version,
    then we would use the repository artifact which is bundled with the NBT
    release on Maven Central.
    melix committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    d4a3a53 View commit details
    Browse the repository at this point in the history
  4. Add release notes

    melix committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    5850c69 View commit details
    Browse the repository at this point in the history

Commits on Oct 12, 2022

  1. Configuration menu
    Copy the full SHA
    02766c5 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    51a72a3 View commit details
    Browse the repository at this point in the history