Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Where is sbt inside Typesafe Activator?

Tags:

I am trying out the Play Framework 2.3.2 using the offline installation with Typesafe Activator 1.2.3. Every piece of documentation tells me that it's using sbt under the covers to build and run projects.

Where is this sbt located/installed? Is it somewhere in the unzipped folder that contained the Activator installation?

How do I start sbt from command line? It's not on the PATH as running locate sbt finds nothing.

like image 562
vektor Avatar asked Aug 01 '14 15:08

vektor


People also ask

How to use activator with an SBT plugin?

An sbt plugin can communicate with Activator’s JavaScript UI using sbt-core-next APIs, so the only need to modify Activator itself will be the pure UI (JS and HTML). For example, to add Activator support for Play Framework, we modified the Play plugin to send an event containing the application URL when the Play server has started up.

What is SBT server in Play Framework?

In addition, sbt server can be a significant optimization (sharing the same JVM and compiler instance among various frontends). When run by Activator 1.3.0, using the new backgroundRun task, the Play Framework’s “dev mode” http server becomes a client of sbt server as well.

What happens when activator runs in Dev Mode?

When run by Activator 1.3.0, using the new backgroundRun task, the Play Framework’s “dev mode” http server becomes a client of sbt server as well. When you run your web app in dev mode, it connects back to sbt server and asks sbt to rebuild when you reload a page.

What's new in activator's UI?

The built-in buttons remain for common tasks (compile, run, test), but the search box at the top of Activator’s UI now autocompletes tasks in addition to source files: We’re now grouping templates based on the Typesafe Reactive Platform in their own category.


1 Answers

The activator-launcher-<version>.jar is actually the sbt launcher with an additional properties file embedded.

If you run activator shell (or any other command you may have used with sbt like compile or package) you're starting sbt itself that in turn executes the commands.

Here's the path of applications that get launched:

  1. activator ui launches the activator UI which launches a sub-sbt process to build
  2. activator new launches the activator template creation terminal application.
  3. activator shell or activator <sbt input> launches sbt itself.

In addition, the activator script attempts to detect if it's run from a "UI" context, e.g. double-clicking from Windows Explorer or OSX Finder. If so, the script will automatically start in UI mode.

like image 145
2 revs, 2 users 75% Avatar answered Sep 21 '22 06:09

2 revs, 2 users 75%