-
Notifications
You must be signed in to change notification settings - Fork 401
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
gradle install
command stops working as soon as the shadow jar plugin is added
#361
Comments
You need to add a classifier, the jar and the shadowJar are using the same artifactId-- this is more of a maven publish plugin thing (really just a configuration thing, but the error gives a hint about the problem). |
@denuno Have the same issue but don't understand your solution. |
workaround can be read here: #347 (comment) |
This should be fixed in the latest version(4.0.2) |
@johnrengelman I am using 4.0.2 with Gradle 4.10.2 and still have the issue. I had to use the mentioned workaround. |
ha. I'm not reading close enough. |
So that we can `./gradlew install` Having source and java doc jars disabled is ok until we release. See: GradleUp/shadow#361 GradleUp/shadow#452
Shadow Version
2.0.2
Gradle Version
4.5.1
Expected Behavior
It should build and install without a problem
Actual Behavior
gradle install command stops working as soon as the shadow jar plugin is added, even though it works fine before that.
Gradle Build Script(s)
Content of Shadow JAR (
jar tf <jar file>
- post link to GIST if too long)The text was updated successfully, but these errors were encountered: