Skip to content
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

docs: add a link to overriding the publishing convention #1152

Merged
merged 2 commits into from
Jul 22, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,15 @@ To support multiple incompatible Scala versions, enable cross building
and do `+ publish` (see [Cross Build][Cross-Build]). See [Resolvers] for other
supported repository types.

### Overriding the publishing convention

By default sbt will publish your artifact with the binary version of Scala
you're using. For example if your project is using Scala 2.13.x your example
artifact would be published under `example_2.13`. This is often what you want,
but if you're publishing a pure Java artifact or a compiler plugin you'll want
to change the `CrossVersion`. See the [Cross Build][Cross-Build] page for more
details under the _Overriding the publishing convention_ section.

### Published artifacts

By default, the main binary jar, a sources jar, and a API documentation
Expand Down