Support for cross-building with Scala Native

Author: lrytz

README.md

@@ -61,7 +61,7 @@ OsgiKeys.exportPackage := Seq(s"<exported package>;version=${version.value}")
 
 Scala versions are defined in `.travis.yml`.
 
-Cross-building with Scala.js is possible, see scala-xml for example.
+Cross-building with Scala.js and Scala Native is possible, see scala-xml or scala-parser-combinators for example.
 
 These additional settings are enabled by `scalaModuleSettings`:
   - `scalacOptions in (Compile, compile) ++= Seq("-feature", "-deprecation", "-unchecked", "-Xlint")`

src/main/scala/ScalaModulePlugin.scala

@@ -40,11 +40,12 @@ object ScalaModulePlugin extends AutoPlugin {
     // The staging profile is called `org.scala-lang`, the default is `org.scala-lang.modules`
     sonatypeProfileName := "org.scala-lang",
 
-    // The staging repository name. The default is `[sbt-sonatype] name version`. We cross-build
-    // using parallel travis jobs, so we include the Scala/Scala.js versions to make them unique.
+    // The staging repository name. The default is `[sbt-sonatype] name version`. We include the
+    // Scala/Scala.js/Scala Native versions to avoid conflicts when running the travis jobs.
     sonatypeSessionName := {
       val sjs = Option(System.getenv("SCALAJS_VERSION")).filter(_.nonEmpty).map(v => s" Scala.js $v").getOrElse("")
-      s"${sonatypeSessionName.value} Scala ${scalaVersion.value}$sjs"
+      val native = Option(System.getenv("SCALANATIVE_VERSION")).filter(_.nonEmpty).map(v => s" Scala Native $v").getOrElse("")
+      s"${sonatypeSessionName.value} Scala ${scalaVersion.value}$sjs$native"
     },
   )