-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Use proper publishing methods. Fix #82. Pin loom. #84
Conversation
// Publish Sources Jar | ||
artifact(tasks.remapSourcesJar.get().archiveFile) { | ||
builtBy(tasks.remapSourcesJar) | ||
this.classifier = "sources" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are sources not part of the kotlin component ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, thats usually done by loom (i.e java { withSourcesJar() }
)
since the dokka artifact already needs to be attached, it makes more sense imo to just leave it here as part of the whole publication
As far as I can tell this looks good to me, results in publishing a gradle module file as well as dependencies in the POM file. Ignore the version numbers, they are from some local testing to compare changes of maven artefacts: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simple changes, LGTM
No description provided.