For any properties you need to change on the command line, prepend them with &quot;set &quot;, and wrap them in quotes.

Example for Windows:

    sbt &quot;set test in assembly := {}&quot; clean assembly

Example for Mac:

    sbt &#39;set test in assembly := {}&#39; clean assembly

While investigating a memory leak I discovered a problem related to the technique of calling `setRootViewController:` inside a transition animation block:

    [UIView transitionWithView:self.window
                      duration:0.5
                       options:UIViewAnimationOptionTransitionFlipFromLeft
                    animations:^{ self.window.rootViewController = newController; }
                    completion:nil];

If the old view controller (the one being replaced) is currently presenting another view controller, then the above code does not remove the presented view from the view hierarchy.

That is, this sequence of operations...

1. X becomes Root View Controller
2. X presents Y, so that Y&#39;s view is on screen
3. Using `transitionWithView:` to make Z the new Root View Controller

...looks OK to the user, but the Debug View Hierarchy tool will reveal that Y&#39;s view is still there behind Z&#39;s view, inside a `UITransitionView`. That is, after the three steps above, the view hierarchy is:

- UIWindow
   - UITransitionView
      - UIView (Y&#39;s view)
   - UIView (Z&#39;s view)

I suspect this is a problem because, at the time of the transition, X&#39;s view isn&#39;t actually part of the view hierarchy.

If I send `dismissViewControllerAnimated:NO` to X immediately before `transitionWithView:`, the resulting view hierarchy is:

- UIWindow
   - UIView (X&#39;s view)
   - UIView (Z&#39;s view)

If I send `dismissViewControllerAnimated:` (YES or NO) to X, then perform the transition in the `completion:` block, then the view hierarchy is correct. Unfortunately, that interferes with the animation. If animating the dismissal, it wastes time; if not animating, it looks broken.

I&#39;m trying some other approaches (e.g., making a new container view controller class to serve as my root view controller) but haven&#39;t found anything that works. I&#39;ll update this question as I go.

The ultimate goal is to transition from the presented view to a new root view controller directly, and without leaving stray view hierarchies around.

Leaking views when changing rootViewController inside transitionWithView

I am trying to setup Unit Testing for my project.
It is an existing Objective-C app, that I have recently added one Swift class to. I have setup the &#39;MyProject-Swift.h&#39; and Swift Bridging files (both &#39;MyProject&#39; and &#39;MyProjectTest&#39;) and I am able to build and run the app just fine using both Objective-C and Swift code.

However, now I want to run some Unit Tests on the new Swift class.
I setup my test file and it looks like the following:

**MySwiftClassTests.swift:**

    import UIKit
    import XCTest
    import MyProject
    
    class MySwiftClassTests: XCTestCase {
    
        override func setUp() {
            super.setUp()
            // Put setup code here. This method is called before the invocation of each test method in the class.
        }
        
        override func tearDown() {
            // Put teardown code here. This method is called after the invocation of each test method in the class.
            super.tearDown()
        }
    
        func testExample() {
            // This is an example of a functional test case.
            XCTAssert(true, &quot;Pass&quot;)
        }
    
        func testPerformanceExample() {
            // This is an example of a performance test case.
            self.measureBlock() {
                // Put the code you want to measure the time of here.
            }
        }
    
    }

I get this error when running the app as Test:

    &#39;MyProject-Swift.h&#39; file not found

I am not sure why this happens only when trying to run the Tests.
Any suggestions?

iOS - &#39;MyProject-Swift.h&#39; file not found when running Unit Tests for Swift

I have read questions: [this][1] and [that][2]. They suggest to modify sbt file. But I want run `sbt clean assembly` without tests and do not modify sbt build files. Is it possible with sbt? In maven there is `-DskipTest=true` parameter, is there analog for sbt?


  [1]: https://stackoverflow.com/questions/9763543/how-can-i-skip-tests-in-an-sbt-build
  [2]: https://stackoverflow.com/questions/22481240/sbt-assembly-skip-specific-test

How run sbt assembly command without tests from command line?

<p>I have read questions: <a href="https://stackoverflow.com/questions/9763543/how-can-i-skip-tests-in-an-sbt-build" target="_blank" rel="noopener noreferrer">this</a> and <a href="https://stackoverflow.com/questions/22481240/sbt-assembly-skip-specific-test" target="_blank" rel="noopener noreferrer">that</a>. They suggest to modify sbt file. But I want run <code>sbt clean assembly</code> without tests and do not modify sbt build files. Is it possible with sbt? In maven there is <code>-DskipTest=true</code> parameter, is there analog for sbt?</p>


I&#39;ve always used Jasmine for my unit tests, but recently I started using Istanbul to give me code coverage reports. I mean I get the *gist* of what they are trying to tell me, but I don&#39;t really know what each of these percentages represent (Stmts, Branches, Funcs, Lines). So far Googling I have been unable to find a solid explanation/resource. 

**Question**: Like I said I get the gist of it, but can someone post either a proper explanation or a link to a proper explanation?

**Tertiary Question**: Is there any way to identify what specific parts of your code aren&#39;t covered? So far without really grokking this report I&#39;m basically guessing.

    -------------------|-----------|-----------|-----------|-----------|
    File               |   % Stmts |% Branches |   % Funcs |   % Lines |
    -------------------|-----------|-----------|-----------|-----------|
       controllers/    |      88.1 |     77.78 |     78.57 |      88.1 |
          dashboard.js |      88.1 |     77.78 |     78.57 |      88.1 |
    -------------------|-----------|-----------|-----------|-----------|
    All files          |      88.1 |     77.78 |     78.57 |      88.1 |
    -------------------|-----------|-----------|-----------|-----------|

How do I read an Istanbul Coverage Report?

In RSpec, specifically version &gt;= 3, is there any difference between:

- Using `allow` to set up message expectations with parameters that return test doubles, and then using `expect` to make an assertion on the returned test doubles
- Just using `expect` to set up the expectation with parameters and return the test double

or is it all just semantics?  I know that providing/specifying a return value with `expect` was [the syntax in RSpec mocks 2.13](https://www.relishapp.com/rspec/rspec-mocks/v/2-13/docs/message-expectations/expect-a-message#provide-a-return-value), but as far as I can see, [the syntax changed in RSpec mocks 3](http://www.relishapp.com/rspec/rspec-mocks/v/3-1/docs/configuring-responses/returning-a-value#specify-a-return-value) to use `allow`. 

However, in the (passing) sample code below, using either `allow`/`expect` or just `expect`/`and_return` seems to generate the same result.  If one syntax was favoured over another, perhaps I would have expected there to be some kind of deprecation notice, but since there isn&#39;t, it would seem that both syntaxes are considered valid:

&lt;!-- language: ruby --&gt;

    class Foo
      def self.bar(baz)
        # not important what happens to baz parameter
        # only important that it is passed in
        new
      end
    
      def qux
        # perform some action
      end
    end
    
    class SomethingThatCallsFoo
      def some_long_process(baz)
        # do some processing
        Foo.bar(baz).qux
        # do other processing
      end
    end
    
    describe SomethingThatCallsFoo do
      let(:foo_caller) { SomethingThatCallsFoo.new }
    
      describe &#39;#some_long_process&#39; do
        let(:foobar_result) { double(&#39;foobar_result&#39;) }
        let(:baz) { double(&#39;baz&#39;) }
    
        context &#39;using allow/expect&#39; do
          before do
            allow(Foo).to receive(:bar).with(baz).and_return(foobar_result)
          end
    
          it &#39;calls qux method on result of Foo.bar(baz)&#39; do
            expect(foobar_result).to receive(:qux)
            foo_caller.some_long_process(baz)
          end
        end
    
        context &#39;using expect/and_return&#39; do
          it &#39;calls qux method on result of Foo.bar(baz)&#39; do
            expect(Foo).to receive(:bar).with(baz).and_return(foobar_result)
            expect(foobar_result).to receive(:qux)
            foo_caller.some_long_process(baz)
          end
        end
      end
    end

If I deliberately make the tests fail by changing the passed-in `baz` parameter in the expectation to a different test double, the errors are pretty much the same:

&lt;!-- language: ruby --&gt;

      1) SomethingThatCallsFoo#some_long_process using allow/expect calls quux method on result of Foo.bar(baz)
         Failure/Error: Foo.bar(baz).qux
           &lt;Foo (class)&gt; received :bar with unexpected arguments
             expected: (#&lt;RSpec::Mocks::Double:0x3fe97a0127fc @name=&quot;baz&quot;&gt;)
                  got: (#&lt;RSpec::Mocks::Double:0x3fe97998540c @name=nil&gt;)
            Please stub a default value first if message might be received with other args as well.
         # ./foo_test.rb:16:in `some_long_process&#39;
         # ./foo_test.rb:35:in `block (4 levels) in &lt;top (required)&gt;&#39;
    
      2) SomethingThatCallsFoo#some_long_process using expect/and_return calls quux method on result of Foo.bar(baz)
         Failure/Error: Foo.bar(baz).qux
           &lt;Foo (class)&gt; received :bar with unexpected arguments
             expected: (#&lt;RSpec::Mocks::Double:0x3fe979935fd8 @name=&quot;baz&quot;&gt;)
                  got: (#&lt;RSpec::Mocks::Double:0x3fe979cc5c0c @name=nil&gt;)
         # ./foo_test.rb:16:in `some_long_process&#39;
         # ./foo_test.rb:43:in `block (4 levels) in &lt;top (required)&gt;&#39;

So, are there any real differences between these two tests, either in result or expressed intent, or is it just semantics and/or personal preference?  Should `allow`/`expect` be used over `expect`/`and_return` in general as it seems like it&#39;s the replacement syntax, or are each of them meant to be used in specific test scenarios?

**Update**

After reading [Mori&#39;s answer](https://stackoverflow.com/a/28007007/567863)&#39;s, I commented out the `Foo.bar(baz).qux` line from the example code above, and got the following errors:

&lt;!-- language: ruby --&gt;

      1) SomethingThatCallsFoo#some_long_process using allow/expect calls qux method on result of Foo.bar(baz)
         Failure/Error: expect(foobar_result).to receive(:qux)
           (Double &quot;foobar_result&quot;).qux(any args)
               expected: 1 time with any arguments
               received: 0 times with any arguments
         # ./foo_test.rb:34:in `block (4 levels) in &lt;top (required)&gt;&#39;
    
      2) SomethingThatCallsFoo#some_long_process using expect/and_return calls qux method on result of Foo.bar(baz)
         Failure/Error: expect(Foo).to receive(:bar).with(baz).and_return(foobar_result)
           (&lt;Foo (class)&gt;).bar(#&lt;RSpec::Mocks::Double:0x3fc211944fa4 @name=&quot;baz&quot;&gt;)
               expected: 1 time with arguments: (#&lt;RSpec::Mocks::Double:0x3fc211944fa4 @name=&quot;baz&quot;&gt;)
               received: 0 times
         # ./foo_test.rb:41:in `block (4 levels) in &lt;top (required)&gt;&#39;

- The `allow` spec fails because the `foobar_result` double never gets to stand in for the result of `Foo.bar(baz)`, and hence never has `#qux` called on it
- The `expect` spec fails at the point of `Foo` never receiving `.bar(baz)` so we don&#39;t even get to the point of interrogating the `foobar_result` double

Makes sense: it&#39;s not just a syntax change, and that `expect`/`and_return` does have a purpose different to `allow`/`expect`.  I really should have checked the most obvious place: the [RSpec Mocks README](https://github.com/rspec/rspec-mocks/blob/master/README.md), specifically the following sections:

- [Mock Objects and Test Stubs](https://github.com/rspec/rspec-mocks/blob/master/README.md#mock-objects-and-test-stubs)
- [Test-Specific Extension](https://github.com/rspec/rspec-mocks/blob/master/README.md#test-specific-extension)
- [Setting Responses](https://github.com/rspec/rspec-mocks/blob/master/README.md#setting-responses)

RSpec allow/expect vs just expect/and_return

I&#39;m creating a simple test within my package directory called reverseTest.go

    package main

    import &quot;testing&quot;

    func TestReverse(t *testing.T) {
	    cases := []struct {
		    in, want string
	    }{
		    {&quot;Hello, world&quot;, &quot;dlrow ,olleH&quot;},
		    {&quot;Hello, 世界&quot;, &quot;界世 ,olleH&quot;},
		    {&quot;&quot;, &quot;&quot;},
	    }

	    for _, c := range cases {
		    got := Reverse(c.in)
		    if got != c.want {
			    t.Errorf(&quot;Reverse(%q) == %q, want %q&quot;, c.in, got, c.want)
		    }
    	}
    }


whenever i try to run it the output is

    exampleFolder[no test files] 

this is my go env

    GOARCH=&quot;amd64&quot;
    GOBIN=&quot;&quot;
    GOCHAR=&quot;6&quot;
    GOEXE=&quot;&quot;
    GOHOSTARCH=&quot;amd64&quot;
    GOHOSTOS=&quot;linux&quot;
    GOOS=&quot;linux&quot;
    GOPATH=&quot;/home/juan/go&quot;
    GORACE=&quot;&quot;
    GOROOT=&quot;/usr/lib/go&quot;
    GOTOOLDIR=&quot;/usr/lib/go/pkg/tool/linux_amd64&quot;
    TERM=&quot;dumb&quot;
    CC=&quot;gcc&quot;
    GOGCCFLAGS=&quot;-g -O2 -fPIC -m64 -pthread&quot;
    CXX=&quot;g++&quot;
    CGO_ENABLED=&quot;1&quot;

Any help will be greatly appreciated. Thanks!!

Golang testing: &quot;no test files&quot;

I am trying to define some endpoints and do a test using `nodejs`. In `server.js` I have:

    var express = require(&#39;express&#39;);
    var func1 = require(&#39;./func1.js&#39;);
    var port = 8080;
    var server = express();
    
    server.configure(function(){
      server.use(express.bodyParser());
    });

    server.post(&#39;/testend/&#39;, func1.testend);

and in `func1.js`:

        var testend = function(req, res) {
               serialPort.write(&quot;1&quot;, function(err, results) {
               serialPort.write(&quot;2&quot; + &quot;\n&quot;, function(err, results) {
               });
          });
       });
        exports.testend = testend;

Now in `test.js` I am trying to use this endpoint:

    var should = require(&#39;should&#39;);
    var assert = require(&#39;assert&#39;);
    var request = require(&#39;supertest&#39;);
    var http = require(&#39;http&#39;);
    var app = require(&#39;./../server.js&#39;);
    var port = 8080;

    describe(&#39;Account&#39;, function() {
            var url = &quot;http://localhost:&quot; + port.toString();
            it(&#39;test starts&#39;, function(done) {
                    request(url).post(&#39;/testend/&#39;)
                    // end handles the response
                    .end(function(err, res) {
                            if (err) {
                                    throw err;
                            }
                            res.body.error.should.type(&#39;string&#39;);
                            done();
                    });
            });
    });

But when I run `node test.js` I am getting this error:

&lt;pre&gt;
describe(&#39;Account&#39;, function() {
^

ReferenceError: describe is not defined
    at Object.&lt;anonymous&gt; (/test/test.js:9:1)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:906:3
&lt;/pre&gt;

How can I fix the issue?


ReferenceError: describe is not defined NodeJs

I have seen it so many times where people suggest to use: 
 
    browser.ignoreSynchronization=true;  // or false

But I do not understand why do we need it?

What is browser.ignoreSynchronization in protractor?

I am getting the following build error when I try and sync my project: 

    Error:(9, 0) Gradle DSL method not found: &#39;compile()&#39;
    Possible causes:The project &#39;AlexTest&#39; may be using a version of Gradle that does not contain the method.
    The build file may be missing a Gradle plugin.
    link: Apply Gradle plugin

I have tried applying every single gradle plugin they link me to in that link on the bottom, yet same issue, so I conclude that the first error is the cause. 

Here is the build.gradle file for AlexTest (the project directory):

    buildscript {
        repositories {
            jcenter()
        }
        dependencies {
            classpath &#39;com.android.tools.build:gradle:0.13.2&#39;
            compile &#39;com.google.android.gms:play-services:6.1.11&#39;
            // NOTE: Do not place your application dependencies here; they belong
            // in the individual module build.gradle files
        }
    }
    
    allprojects {
        repositories {
            jcenter()
        }
    }

I think that was the gradle file it was having trouble with. But I&#39;m not sure what method it is referring to. 

Also here is the gradle-wrapper.properties which it also referred to:

    #Mon Nov 10 01:06:12 PST 2014
    distributionBase=GRADLE_USER_HOME
    distributionPath=wrapper/dists
    zipStoreBase=GRADLE_USER_HOME
    zipStorePath=wrapper/dists
    distributionUrl=https\://services.gradle.org/distributions/gradle-2.1-all.zip

perhaps the gradle version in the distributionUrl needs to match the one in the dependency?

I also have a build.gradle file in the app directory itself - 1 level lower, though I don&#39;t think that is what it was referring to, but here it is: 


    apply plugin: &#39;com.android.application&#39;
    
    android {
        compileSdkVersion 20
        buildToolsVersion &quot;21.1.1&quot;
    
        defaultConfig {
            applicationId &quot;com.snappiesticker.alextest&quot;
            minSdkVersion 16
            targetSdkVersion 20
            versionCode 1
            versionName &quot;1.0&quot;
        }
        buildTypes {
            release {
                runProguard false
                proguardFiles getDefaultProguardFile(&#39;proguard-android.txt&#39;), &#39;proguard-rules.pro&#39;
            }
        }
    }
    
    dependencies {
        compile fileTree(dir: &#39;libs&#39;, include: [&#39;*.jar&#39;])
        compile &#39;com.google.android.gms:play-services:6.1.+&#39;
    }




Android gradle build Error:(9, 0) Gradle DSL method not found: &#39;compile()&#39;.

My Xcode project using a storyboard entered in a very weird state recently: Xcode keeps building the whole project and notably the storyboard after *each keypress*. I found no reason for this behavior neither in my project diffing all interesting files (storyboard and project) neither a setting in Xcode (maybe I just could not find it?) Needless to say that this &quot;feature&quot; makes working on my project nearly impossible since the CPU is constantly occupying with rebuilding the storyboard when I type new code. Anybody seen this?

Xcode keeps building storyboard after each keystroke

I have some things for development - e.g mocks which I would like to not bloat my distributed build file with.

In RequireJS you can pass a config in a plugin file and conditonally require things in based on that.

For webpack there doesn&#39;t seem to be a way of doing this. Firstly to create a runtime config for an environment I have used [resolve.alias][1] to repoint a require depending on the environment, e.g:

    // All settings.
    var all = {
    	fish: &#39;salmon&#39;
    };
    
    // `envsettings` is an alias resolved at build time.
    module.exports = Object.assign(all, require(&#39;envsettings&#39;));

Then when creating the webpack config I can dynamically assign which file `envsettings` points to (i.e. `webpackConfig.resolve.alias.envsettings = &#39;./&#39; + env`).

However I would like to do something like:

    if (settings.mock) {
    	// Short-circuit ajax calls.
    	// Require in all the mock modules.
    }

But obviously I don&#39;t want to build in those mock files if the environment isn&#39;t mock.

I could possibly manually repoint all those requires to a stub file using resolve.alias again - but is there a way that feels less hacky?

Any ideas how I can do that? Thanks.

  [1]: http://webpack.github.io/docs/configuration.html#resolve-alias

Conditional build based on environment using Webpack

I&#39;ve been playing with webpack and during the build I see it output:
`+ 27 hidden modules`. What does it mean by this? Is it detecting global constants that I&#39;m using without requiring them?

What does webpack mean by XX hidden modules

How do I install/upgrade [gradle][1] for Mac?


  [1]: https://gradle.org/

Install / upgrade gradle on Mac OS X

I&#39;m using SBT (within IntelliJ IDEA) to build a simple Scala project.

I would like to know what is the **simplest way** to build an **Uber JAR** file (aka Fat JAR, Super JAR).

I&#39;m currently using SBT but when I&#39;m submiting my JAR file to [Apache Spark][1] I get the following error:

&gt; Exception in thread &quot;main&quot; java.lang.SecurityException: Invalid
&gt; signature file digest for Manifest main attributes

Or this error during compilation time:

&gt; java.lang.RuntimeException: deduplicate: different file contents found
&gt; in the following:&lt;br&gt;
&gt; PATH\DEPENDENCY.jar:META-INF/DEPENDENCIES&lt;br&gt;
&gt; PATH\DEPENDENCY.jar:META-INF/MANIFEST.MF

It [looks like][2] it is because some of my dependencies include signature files (META-INF) which needs to be removed in the final Uber JAR file.

I tried to use the [sbt-assembly][3] plugin like that:

/project/assembly.sbt

    addSbtPlugin(&quot;com.eed3si9n&quot; % &quot;sbt-assembly&quot; % &quot;0.12.0&quot;)

/project/plugins.sbt

    logLevel := Level.Warn

/build.sbt

    lazy val commonSettings = Seq(
      name := &quot;Spark-Test&quot;
      version := &quot;1.0&quot;
      scalaVersion := &quot;2.11.4&quot;
    )
    
    lazy val app = (project in file(&quot;app&quot;)).
      settings(commonSettings: _*).
      settings(
        libraryDependencies ++= Seq(
          &quot;org.apache.spark&quot; %% &quot;spark-core&quot; % &quot;1.2.0&quot;,
          &quot;org.apache.spark&quot; %% &quot;spark-streaming&quot; % &quot;1.2.0&quot;,
          &quot;org.apache.spark&quot; % &quot;spark-streaming-twitter_2.10&quot; % &quot;1.2.0&quot;
        )
      )

When I click &quot;*Build Artifact...*&quot; in IntelliJ IDEA I get a JAR file. But I end up with the same error...

I&#39;m new to SBT and not very experimented with IntelliJ IDE.

Thanks.


  [1]: https://spark.apache.org/
  [2]: https://groups.google.com/forum/#!topic/spark-developers/1H6bfiCeTaY
  [3]: https://github.com/sbt/sbt-assembly

How to build an Uber JAR (Fat JAR) using SBT within IntelliJ IDEA?

**TL;DR:** How can I fully reconcile all dependencies in IntelliJ when SBT file changes

I have a SBT project setup in IntelliJ. For the most part if works like a charm, but it is quite a pain for me, to change the version of the dependencies and compilers.

What I hope to do, is to update my SBT file, and click something like *clean project* in IntelliJ, so it gets up to date.

The best menu item I have found is *Rebuild project*. It reads new dependencies, but keeps the old ones around, so External Libraries contains multiple versions of the Scala runtime and 3rd party libraries.

To get around this I can close IntelliJ and delete all files in `.idea/libraries`. When I restart IntelliJ it will re-resolve the dependencies. It works, but manually deleting metadata files indicates that I am doing the wrong thing.

How to fully clean, re-resolve and rebuild a Scala sbt-managed project in IDEA?

Similar problem with https://stackoverflow.com/questions/26582300/how-to-use-sbt-behind-authenticated-proxy. I tried with the given answer and problem still there. 

When I run **sbt** in terminal, it shows and stucks at : 

    Getting org.scala-sbt sbt 0.13.6 ...

additional information: 

     sbt --version
     sbt launcher version 0.13.6

How could I fix it?


stuck at &quot;Getting org.scala-sbt sbt 0.13.6 ...&quot; when running sbt in terminal

This question may sound silly for you, but I have been searching the Internet for a while and couldn&#39;t find the answer. How can I open SBT Tool Window in Intellij (scala and SBT plugins obviously installed)?



How to open SBT Tool Window in Intellij?

I created a new Play Framework project using the activator, `activator new my-project-name` and  then I selected the `play-java` template and the project is created with no errors.

Then I import the project into my IDE, IntelliJ, as a SBT project. When the project is imported a popup is shown saying: `SBT compilation for play framework 2.x disabled by default`.

On IntelliJ project&#39;s panel it doesn&#39;t show all (mostly the files with the code) files. Just a handful of them.

[![enter image description here][1]][1]

The build.sbt file looks like full of compilation error (pretty much all the lines are red underlined).

Here&#39;s the build.sbt file

    name := &quot;&quot;&quot;my-project-name&quot;&quot;&quot;
    
    version := &quot;1.0-SNAPSHOT&quot;
    
    lazy val root = (project in file(&quot;.&quot;)).enablePlugins(PlayJava)
    
    scalaVersion := &quot;2.11.6&quot;
    
    libraryDependencies ++= Seq(
      javaJdbc,
      cache,
      javaWs
    )
    
    // Play provides two styles of routers, one expects its actions to be injected, the
    // other, legacy style, accesses its actions statically.
    routesGenerator := InjectedRoutesGenerator
    
    
    fork in run := true

I can compile and run the code with `activator ui` with no errors. So, why isn&#39;t IntelliJ fully importing the project and it shows me `SBT compilation for play framework 2.x disabled by default` message?

I googled around and couldn&#39;t find any hint related to this so I&#39;m kinda lost here. 


**EDIT: -------------------------------------**

I closed the project on IntelliJ and deleted the project folder. Closed IntelliJ and using `activator` I created again the same project. Using `activator ui` I compiled the project. Then I fired up IntelliJ and was prompted to either open a project, create a new one or import a project.

Selected import a project and did the normal &quot;import a project steps&quot; and IntelliJ imported the project with no hassle. **But** if I try to import the project while with an open project on IntelliJ I get the same problem that lead me to make this question. Maybe this is a bug on IntelliJ?


**EDIT 2 ------------------------------------------**

The solution to these two problems (the &quot;*SBT compilation for play framework 2.x disabled by default*&quot; and the files not showing on IntelliJ) can be fixed with `user3384225` and `DarkShadow` answers.

  [1]: http://i.stack.imgur.com/LRvz5.png

Content Type	Original Author	Original Content on Stackoverflow
Question	Cherry	View Question on Stackoverflow
Solution 1 - Testing	kshakir	View Answer on Stackoverflow

How run sbt assembly command without tests from command line?

Testing Problem Overview

Testing Solutions

Solution 1 - Testing

iOS - 'MyProject-Swift.h' file not found when running Unit Tests for Swift

Leaking views when changing rootViewController inside transitionWithView

Attributions