Deploys sbt-artifacts using Eclipse aether. Aether is the same library as maven itself uses, meaning that the same behaviour should be expected.
...
addSbtPlugin("no.arktekk.sbt" % "aether-deploy" % "0.14")
...
If you see errors similar to what is described in this ticket arktekk#25 then you might want to check if you are using a global plugin.
There are known incompabilities with sbt-pgp
if sbt-pgp is used as a global plugin.
publishTo <<= (version: String) {
if (version.endsWith("SNAPSHOT")) {
Some("Sonatype Nexus Snapshots" at "https://oss.sonatype.org/content/repositories/snapshots")
} else {
Some("Sonatype Nexus Staging" at "https://oss.sonatype.org/service/local/staging/deploy/maven2")
}
}
This plugin is now an Autoplugin, so there is no need to add extra config to make it work.
overridePublishSettings
overridePublishLocalSettings
overridePublishBothSettings
credentials += Credentials(Path.userHome / ".sbt" / ".credentials")
To deploy to remote Maven repository.
sbt aether-deploy
To deploy to local maven repository.
sbt aether-install
To deploy to remote Maven repository.
sbt publish
To deploy to local maven repository.
sbt publish-local
Documentation for proxies can be found here
You will need to add the sbt-pgp-plugin as described here.
enablePlugins(SignedAetherPlugin)
disablePlugins(AetherPlugin)
This should now allow aether-deploy task to work with the sbt-pgp-plugin
overridePublishSignedSettings
overridePublishSignedLocalSettings
overridePublishSignedBothSettings