[英]Extending “universal” configuration in sbt-native-packager
I'm working with sbt 0.13.8 and sbt-native-packager 1.0.3. 我正在使用sbt 0.13.8和sbt-native-packager 1.0.3。
I'd like to to set up a development and production packaging configuration with different java options. 我想使用不同的Java选项设置开发和生产包装配置。 The idea is creating a package tarball through
UniversalPluguin
from sbt-native-packager : "universal:packageZipTarball"
. 这个想法是通过
sbt-native-packager : "universal:packageZipTarball"
UniversalPluguin
创建一个软件包tarball sbt-native-packager : "universal:packageZipTarball"
。 I'm also using the " JavaServerAppPackaging
" archetype. 我还使用“
JavaServerAppPackaging
”原型。
I tried this Build.scala
: 我尝试了这个
Build.scala
:
import sbt._
import Keys._
import com.typesafe.sbt.packager.universal.UniversalPlugin.autoImport._
import com.typesafe.sbt.packager.archetypes.JavaServerAppPackaging
object Build extends Build {
lazy val commonSettings: Seq[Setting[_]] = Seq(
scalaVersion := "2.11.7",
crossScalaVersions := Seq("2.11.7"),
scalacOptions in Compile ++= Seq( "-unchecked", "-feature", "-language:postfixOps", "-deprecation" )
)
lazy val devConfig = config("dev") extend Universal
lazy val prodConfig = config("prod") extend Universal
lazy val root = (project in file("."))
.settings(commonSettings : _*)
.enablePlugins(JavaServerAppPackaging)
.configs(devConfig, prodConfig)
.settings(
javaOptions in devConfig ++= Seq(
// -J params will be added as jvm parameters
"-J-Xmx384m",
"-J-Xss512k"),
javaOptions in prodConfig ++= Seq(
// -J params will be added as jvm parameters
"-J-Xmx384m",
"-J-Xss740k")
)
}
With that setup, SBT keeps failing with: 通过该设置,SBT始终失败:
Error:Error while importing SBT project:
...
at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1310)
at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
at sbt.std.Transform$$anon$4.work(System.scala:63)
at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
at sbt.Execute.work(Execute.scala:235)
at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
at sbtConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[error] java.text.ParseException: unknown configuration 'universal'. It is extended by dev in null
[error] Use 'last' for the full log.
See complete log in /Users/ivan/Library/Logs/IdeaIC14/sbt.last.log
I'm behind the idea of creating two packaged tarball for development with sbt command " dev:packageZipTarball
", and for production with " prod:packageZipTarball
" with different jvm options. 我支持使用sbt命令“
dev:packageZipTarball
”开发两个打包的tarball以及使用带有不同jvm选项的“ prod:packageZipTarball
”来生产的prod:packageZipTarball
。
Any ideas why I can't extend " universal
" configuration with custom configurations in order to achieve that or alternatives to that approach? 有什么想法为什么我不能使用自定义配置扩展“
universal
”配置以实现该方法或该方法的替代方法?
I highly recommend against extending configurations . 我强烈建议不要扩展配置 。 The behaviour is not the expected one.
该行为不是预期的。 The best way to achieve different build configurations is to create submodules for each configuration.
实现不同构建配置的最佳方法是为每个配置创建子模块 。
See this answer that explains in more detail how to create subprojects with different configurations. 请参阅此答案 , 该答案更详细地说明了如何创建具有不同配置的子项目。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.