-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Publish reobfuscated jar #206
Comments
basically, technically, yes; youd' need to figure out how to tell it to publish the artifact without a classifier; but, generally, we don't recommend doing that, just specify the dev classifier when targeting it |
Appreciate your fast response ;) I now understood that i shouldn't replace the non-dev version with the dev version but specify the classifier. Thanks for your help 😃! |
Currently i configured the reobfJar to run always after the jar task, which means if i build the project it creates the reobf. Jar. If i publish it, it creates the reobfuscated jar before signing and publishing. However the reobf. jar still doesn't end up in the remaining task chain. (At least i think so because it doesn't get published). |
See #137 (comment) and #177; Changes to how userdev interacts with publishing are planned, but there's significant work and decisions to be made. |
I am currently developing an API for spigot, which I want to publish on a Nexus Repository.
However Nexus complains about not finding the main jar file.
This makes sense because it publishes only the -dev.jar file.
In my publish configuration I set the java component to be published by using
from(components["java"])
Is there any way to publish the unobfuscated version but without the -dev?
If I understood things wrong I apologize and hope for help :)
Have a great day 😃
The text was updated successfully, but these errors were encountered: