There's a difference between the module files i get from jitpack and locally by maven, in regards to classifiers.
For example, starting with this dependency (notice the natives-desktop classifier):
dependencies { api group: 'com.badlogicgames.gdx', name: 'gdx-backend-lwjgl3', version: '1.9.10' api "com.badlogicgames.gdx:gdx-platform:1.9.10:natives-desktop" }
i get the following in the module file when building locally:
When built on jitpack, i get this (it misses the artifactSelector):
{ "group" : "com.badlogicgames.gdx", "module" : "gdx-platform", "version" : { "requires" : "1.9.10" } }
You can see an example here.
This problems causes issues when generating the classpath, for example with "sourceSets.main.runtimeClasspath.getAsPath()", for example in a run task.
To Reproduce
Steps to reproduce the behavior:
create a gradle project with a dependency with classifier
run gradle publishToMavenLocal and observe the correct .module
run jitpack on it
observe the different .module
Expected behavior
It should generate a correct .module file. As far as i have observed, if a dependency is in the gradle cache (.gradle\caches\modules-2\files-2.1) it needs a correct module file to generate the correct classpath, while if it is on the maven cache (.m2\repository) it works correctly.
Describe the bug
There's a difference between the module files i get from jitpack and locally by maven, in regards to classifiers. For example, starting with this dependency (notice the natives-desktop classifier):
dependencies { api group: 'com.badlogicgames.gdx', name: 'gdx-backend-lwjgl3', version: '1.9.10' api "com.badlogicgames.gdx:gdx-platform:1.9.10:natives-desktop" }
i get the following in the module file when building locally:
{ "group": "com.badlogicgames.gdx", "module": "gdx-platform", "version": { "requires": "1.9.10" }, "thirdPartyCompatibility": { "artifactSelector": { "name": "gdx-platform", "type": "jar", "extension": "jar", "classifier": "natives-desktop" } } }
When built on jitpack, i get this (it misses the artifactSelector):
{ "group" : "com.badlogicgames.gdx", "module" : "gdx-platform", "version" : { "requires" : "1.9.10" } }
You can see an example here.This problems causes issues when generating the classpath, for example with "sourceSets.main.runtimeClasspath.getAsPath()", for example in a run task.
To Reproduce Steps to reproduce the behavior:
Expected behavior
It should generate a correct .module file. As far as i have observed, if a dependency is in the gradle cache (.gradle\caches\modules-2\files-2.1) it needs a correct module file to generate the correct classpath, while if it is on the maven cache (.m2\repository) it works correctly.