-
Notifications
You must be signed in to change notification settings - Fork 400
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
"-all" classifier dropped from published jar #860
Comments
I've tracked this down to changes in 960617f..a6399e2 (the intermediate commits produce errors). At a glance, I don't see any obvious things that caused the classifier do be omitted, then again I'm not familiar at all with this codebase. @Goooler the changes were made by you, do you know what could have caused this issue? |
As far as I can tell The problem only arises when publishing to local or remote repositories. I'm guessing this means that |
…GradleUp/shadow#860 - published artifacts lack -aws suffix.
In 960617f, the artifact addition was changed in publication.artifact(project.tasks.named("shadowJar")) to publication.artifact(archiveFile.get()) where The docs of MavenPublication#artifact give different behaviour for different input types:
Could it be that the classifier is not interpolated correctly from the file name? EDIT: Indeed, the artifact returned by |
I've published the fix from #904 in my fork, you can try https://plugins.gradle.org/plugin/io.github.goooler.shadow |
GradleUp/shadow#860 says this is a bug in shadow 8.1.1. Revert to 8.1.0 until there's a fix available.
GradleUp/shadow#860 says this is a bug in shadow 8.1.1. Revert to 8.1.0 until there's a fix available.
When publishing a Maven artifact using Shadow 8.1.1, the "-all" classifier is dropped from the jar file.
This happens for both local publishing and to remote repositories, too.
Shadow Version
8.1.1
Gradle Version
8.1
Expected Behavior
Building using Shadow 8.1.0
produces the following artifacts:
Actual Behavior
Building with Shadow 8.1.1
produces the following artifacts:
Note that the jar is lacking the
-all
qualifier.In both cases, i.e. with Shadow 8.1.0 as well as the new 8.1.1, the shadow-jar of the application's
build
directory correctly contains the-all
classifier:Gradle Build Script(s)
Note that the line
archiveClassifier.set("all")
is not relevant: the same problem occurs when it is missing.Content of Shadow JAR (
jar tf <jar file>
- post link to GIST if too long)I don't think this is relevant, since the content is fine. Let me know if I should supply it.
The behavior can be reproduced using a default
Application.kt
file.The text was updated successfully, but these errors were encountered: