You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
I discovered that my project was configuring publishing before the actual shadowJar, which was causing the wrong classifier to get picked up by the shadow plugin. Is this a reasonable situation that could be improved with lazy evaluation, or should I restructure my build file to configure shadowJar first?
Shadow Version
8.1.4-8.1.7
Gradle Version
8.8
Expected Behavior
The archive published has the classifier that I specified in shadowJar archiveClassifier
I discovered that my project was configuring publishing before the actual shadowJar, which was causing the wrong classifier to get picked up by the shadow plugin. Is this a reasonable situation that could be improved with lazy evaluation, or should I restructure my build file to configure shadowJar first?
Shadow Version
8.1.4-8.1.7
Gradle Version
8.8
Expected Behavior
The archive published has the classifier that I specified in shadowJar archiveClassifier
Actual Behavior
The archiveClassifier is
all
Gradle Build Script(s)
See this modified unit test in my fork, which is failing: https://github.com/gharris1727/shadow/blob/c08186d96fe9ce4799f67660c03ac34c65fc61c3/src/test/groovy/com/github/jengelman/gradle/plugins/shadow/PublishingSpec.groovy#L81-L127
Content of Shadow JAR (
jar tf <jar file>
- post link to GIST if too long)N/A
The text was updated successfully, but these errors were encountered: