Jitpack generates wrong Gradle metadata

[elect86]

Describe the bug

Wrong Gradle metadata generated from build

To Reproduce
Steps to reproduce the behavior:

1. trigger a new build of kool
2. Check the .module metadata file, this is wrong

    "dependencies" : [ {
      "group" : "kx.platform",
      "module" : "source",
      "version" : {
        "requires" : "0.0.9"
      }
    }, {

Expected behavior

Run the very same command locally, you should get instead the following

      "dependencies": [
        {
          "group": "kx.platform",
          "module": "source",
          "version": {
            "requires": "0.0.9"
          },
          "attributes": {
            "org.gradle.category": "platform"
          },
          "endorseStrictVersions": true
        },

This is a blocker, because downstream will cause the Idea Gradle project reload to fail because kx.platform:source:0.0.9 will be seen as a normal dependency instead of a platform

[skalarproduktraum]

I am having the same issue. Any chance for this getting fixed? Thanks 👍

[breandan]

cc: @jitpack

[elect86]

For anyone having this problem, there may be a solution: in your project instead adding the dependency to a classic platform

implementation(platform("sciJava:platform:30.0.0+6"))

just apply a plugin which defines the constraints

This can play well with Gradle 7.0 catalogs with this workaround

[ljjh20]

I have the same issue.

[skalarproduktraum]

I have found a workaround: It works by disabling the Gradle metadata entirely, as the POM created as actually correct.

Here's the snippet that needs to be added to the build.gradle.kts:

if(System.getenv("JITPACK") != null) {
    tasks.withType<GenerateModuleMetadata> {
        enabled = false
    }
}

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.