Description of problem: Current fedora sbt package uses a custom launch script that does not support options provided by upstream. You can find in the upstream rpm package at: http://www.scala-sbt.org/0.13/tutorial/Installing-sbt-on-Linux.html Launch scripts are available at: https://github.com/sbt/sbt-launcher-package Version-Release number of selected component (if applicable): sbt-0.13.1-5.fc20 Current fedora package can probably be used to build rpm packages for some scala based projects, but it can not be used by scala developers for their daily job.
(In reply to Olivier Samyn from comment #0) > Description of problem: > Current fedora sbt package uses a custom launch script that does not support > options provided by upstream. You can find in the upstream rpm package at: > http://www.scala-sbt.org/0.13/tutorial/Installing-sbt-on-Linux.html Thanks for the report. While we can't use the upstream launch script in Fedora, we can probably figure out how to add the features in particular that you're missing. What command-line options do you need? > Current fedora package can probably be used to build rpm packages for some > scala based projects, but it can not be used by scala developers for their > daily job. I use it for scala development on Fedora. I'd be interested to hear what problems you're having.
Thanks for your quick answer. I mainly develop Play based web applications that sometimes uses quite complex build involving sub-modules and external dependencies. The problem I faced that triggered this bug report is that I had to run my application in debug mode without a way to specify that on the sbt command line. Aside of that, there is another bug #1083130 that asks to be able to specify memory options. This is a second canditate. So, here is a small "wishlist" from the help options of upstream scripts: -d | -debug set sbt log level to debug -no-colors disable ANSI color codes -sbt-dir <path> path to global settings/plugins directory (default: ~/.sbt) -sbt-boot <path> path to shared boot directory (default: ~/.sbt/boot in 0.11 series) -ivy <path> path to local Ivy repository (default: ~/.ivy2) -mem <integer> set memory options (default: 1536, which is -Xms1536m -Xmx1536m -XX:MaxPermSize=384m -XX:ReservedCodeCacheSize=192m) -jvm-debug <port> Turn on JVM debugging, open at the given port. -java-home <path> alternate JAVA_HOME Aside of that, the script should also support environment variables: JAVA_OPTS and SBT_OPTS and passing variables to the java runtime (-Dkey=val and -J-X)
Thanks for the feedback! I'll be working on sbt fixes for Fedora (and improved integration with Fedora as well) soon. If you need a workaround in the meantime and won't be using sbt to package for Fedora, I'd recommend installing the sbt-extras script (https://github.com/paulp/sbt-extras), perhaps as "xsbt," and using that.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.