Categories


opensource software

SBT

Products: IntelliJ IDEA

Vendor: Esko Luontola

Email: N/A

Website: http://github.com/orfjackal/idea-sbt-plugin

License: http://github.com/orfjac...n/raw/master/LICENSE.txt

Bugtracker page

Description:

Integrates with Simple Build Tool (SBT) to enable building Scala projects easily and quickly.

Offers a console where SBT commands can be entered interactively, and a Before Run task to delegate project compilation to SBT, as an alternative to the built in IntelliJ Make.

Documentation, Screenshots

Downloads: 185404
Rating:
Participated in rating: 9
Version Since Build Until Build File/URL Size (Kb) Date Details
1.6.1. 135.475. . Download 1471.5 2014-05-14 21:16:23 details
1.5.1. 122.327. . Download 1473.35 2013-10-17 15:00:54 details
1.4.0. 103.255. . Download 1459 2012-09-24 00:56:40 details
1.1.0. 95.66. . Download 484.66 2010-12-02 22:07:12 details
. .
6 updates are hidden show all updates

Recent change notes:

Fix dependency to allow installation on IntellIJ IDEA 0.13.0

General usage instructions:

Go to the "Before launch" options of a Run Configuration, uncheck "Make" and choose "Run SBT Action / test-compile" to compile the project with SBT.

This plugin does not generate or synchronize your IDEA project structure from the SBT build configuration. The sbt-idea-plugin (http://github.com/mpeltonen/sbt-idea-plugin), a plugin for SBT, rather than for IDEA, serves this purpose. These two projects are complementary, and do not conflict with each other.

Alternatively you can rely on IDEA's Maven integration, so that both SBT and IDEA find the dependencies from Maven's POM files. But beware that SBT/Ivy does not support the relativePath element for parent POMs (https://issues.apache.org/jira/browse/IVY-1173), which can cause issues with multi-module projects.

Comments:

12>
mschwerhoff
Rated:
2014-04-03 16:19:10
Is there a way to configure the SBT Console view (in IDEA CE 13.1 EAP) to correctly display Unicode characters (UTF-8) that are printed when running the program under development? Currently, instead of Unicode characters, e.g., greek letters, I see output such as "σ" or "γ". In my experience, this hints at not having the right encoding options set, rather than not using appropriate fonts. When I start sbt directly on the command-line of Windows, and run my program, then Unicode characters are displayed correctly. I added "-Dfile.encoding=UTF-8" to the VM options of Settings -> SBT, and also tried various fonts for the SBT Console view, but without success. Thanks (also for the great plugin in general), Malte
.
bhuddleston42
Rated:
2013-07-16 22:37:32
I too would be interested in being able to send a ^D so I could conveniently use the SBT plugin for Play. Using the skull to terminate the session works but is a bit cumbersome.
.
naree.song
Rated:
2013-07-11 19:44:55
Hello, I am using SBT plugin(v. 1.5.0) to run a Play application with IntelliJ. I run the app using run command inside the SBT Console. In order to stop the Play app, I need to press Ctrl+D. However, this does not work in SBT plugin. I have to press the skeleton button to forcibly kill the sbt process. If I run the Play app in SBT Console in command line, Ctrl+D works fine and stops the app and takes me back to the console. Any idea how I can get Ctr+D working with SBT plugin? Thanks, Naree
.
retronymster
2012-09-24 18:22:44
virgo47: Please try the latest plugin update (1.4.0). The SBT console won't pop up when you load the project. It is still available in non-Scala projects, as SBT isn't just a build tool for Scala.
.
virgo47
Rated:
2012-09-19 09:48:43
Would it be possible to hide SBT Console panel button in non-Scala projects?
.
brunovernay
Rated:
2012-01-04 17:38:55
.
ORFJackal
2011-04-22 00:00:51
The history can be accessed with Alt+Up
.
ORFJackal
2011-02-23 11:59:49
The history is not accessible.
.
Anonymous
Rated:
2011-02-23 05:27:34
How do you access your sbt history, what you would do by pressing up-arrow in a normal terminal in the SBT Plugin's Console?
.
philip142au
Rated:
2010-10-11 08:07:10
.
Anonymous
Rated:
2010-08-03 13:58:45
I had trouble with scala 2.8.0 and found one simple way to fix it:

- replace the scala plugin lib with the newest 2.8.0.final ones. On my machine this is in "C:\Documents and Settings\mylogin\.IntelliJIdea90\config\plugins\Scala\lib"

- then simply add a dependency on the scala 2.8.0.final lib in the "module settings", and it's just fine! (with "export" unticked, "compile" mode)

Hope it helps,

JL
.
ORFJackal
2010-07-28 00:00:14
The SBT project files are needed, because otherwise the plugin can't run. The SBT plugin doesn't need the POM file, but if you want to have the dependencies configured in IDEA, you will either need to do it manually or use IDEA's Maven plugin which needs the POM file.
.
ittayd
2010-07-27 12:09:20
So in order to use the plugin I need both an SBT project and a POM file?
.
ORFJackal
2010-07-23 23:36:22
Yes, the plugin always launches SBT in the IDEA project's base directory, so the SBT project needs to be there. If you want to improve the plugin, the method where SBT's working directory is chosen is in net.orfjackal.sbt.plugin.SbtRunnerComponent#startIfNotStarted

For me the show stopper for using SBT in multi-module projects is that SBT relies on Ivy's POM file parsing, and Ivy does not recognize the relativePath element in the POM's parent element. As a result SBT cannot compile multi-module Maven projects.

There are two solutions, but for neither of which I have the time:

1. Fix Ivy to recognize the relativePath element

2. Improve this SBT plugin to import dependencies from SBT into IDEA

Option 1 is probably easier.
.
Anonymous
2010-07-23 22:49:27
I think I see the problem that I was having with tests, as well as the general problem I was experiencing with the plugin where it would act like SBT had not been run yet.

Basically, I have a project with multiple modules, like so:
Scala
--- App1
--- App2

App1 had been set up originally with sbt from the command line. For App1 I have a Run Configuration set such that the main class is Main, the working directory is \someplace\Scala\App1, and the classpath is App1, with the Run SBT before launch action of course.

The plugin, when I tell it to compile App1, first apparently looks to see if there is a SBT project declared at the Scala level. This seems like a bug to me and is a show stopper. For now I guess I'll continue to use sbt at the command line.

Best regards,


Steve Thompson
--
.
12>