To help prevent the 504's that happen often when Gradle searches for the -sources jar, the user now has to directly define the classifiers for them to show up.
This is a much more robust solution than the searching for +1 file ids and checking the file name like before.
Given the project curse.maven:myproject-99999:12345, you now have to directly define the source jar. In this example, let's assume it exists at the file id 12346. Also add api jar at 12347. We now define the Gradle string as: curse.maven:myproject-99999:12345-sources-12346-api-12347.
In the future, I could make This is made much shorter by allowing for sequential file ids to just be ommited. In this example, we'd do curse.maven:myproject-99999:12345-sources-api, and infer that the sources is +1 of the main id, and the api is +2 of the main (or +1 of the sources)
To help prevent the 504's that happen often when Gradle searches for the -sources jar, the user now has to directly define the classifiers for them to show up. This is a much more robust solution than the searching for +1 file ids and checking the file name like before. Given the project
curse.maven:myproject-99999:12345, you now have to directly define the source jar. In this example, let's assume it exists at the file id12346. Also add api jar at12347. We now define the Gradle string as:curse.maven:myproject-99999:12345-sources-12346-api-12347.In the future, I could makeThis is made much shorter by allowing for sequential file ids to just be ommited. In this example, we'd docurse.maven:myproject-99999:12345-sources-api, and infer that the sources is +1 of the main id, and the api is +2 of the main (or +1 of the sources)