[ST2.1.1][CMD 3.1.0.256] Failed building SASS with system ruby

[robert_k]

REQUIRED INFORMATION

Sencha Cmd version(s) tested:

• Sencha Cmd 3.1.0.256

Operating System:

• OS X 10.6.8

Framework used:

• Sencha Touch 2.1.1

Description:

• sencha app build testing
• [INF] executing compass using system installed ruby runtime
• error app.scss (Line 90: Invalid CSS after "}": expected selector or at-rule, was "%disclosure {")

Steps to reproduce the problem:

This error didn't happen with the last version of Sencha Cmd 3.0. I can manually go to my resources/sass directory and successfully run "compass compile" from there. It appears that Sencha Cmd is having trouble with @extend-only selectors.

Just include a placeholder rule to your app.scss:

%shared {
  color: blue;
}

.foo {
  @extend %shared;
  font-size: 12px;
}

/Users/[user]/Code/[project]/front-end/sencha app build testing > error.log

The logfile is here: error.txt

The result that was expected:

• It should've compiled like usual.

The result that occurs instead:

• Compilation fails, of course.
• I think Sencha Cmd actually used an internal jRuby/Compass, or the default Mac OS X version of Ruby, rather than the system Ruby that is set via rbenv (should be easily available via "/usr/bin/env ruby").

[mitchellsimoens]

Thanks for the report! I have opened a bug in our bug tracker.

[themightychris]

I've run into this problem as well, it appears that CMD 3.1 ships with a really old version of SASS (3.1.7) while 3.0 used the newer version installed on my system. I'm looking for a clean way to override the compass binary path via sencha.cfg somewhere, is there a setting?

[robert_k]

The only way I was able to work around this was to revert to Sencha CMD 3.0.2. I wasn't able to come up with a way to keep the newest version of Sencha CMD.

[themightychris]

I've got the newest CMD using my system gems with this ugly hack:

1) Rename /usr/local/bin/Sencha/Cmd/3.1.0.256/extensions/sencha-compass/gems to gems.bak
2) Create empty directory in its place
3) Fill with symlinks:

lrwxrwxrwx 1 root root 14 Apr  8 14:26 bin -> /usr/local/bin
lrwxrwxrwx 1 root root 36 Apr  8 14:25 cache -> /usr/local/lib64/ruby/gems/1.8/cache
lrwxrwxrwx 1 root root 35 Apr  8 14:25 gems -> /usr/local/lib64/ruby/gems/1.8/gems
lrwxrwxrwx 1 root root 45 Apr  8 14:25 specifications -> /usr/local/lib64/ruby/gems/1.8/specifications

[themightychris]

@mitchellsimoens - can we just get a version bump for the sass gem in the next CMD build to 3.2.7?

[robert_k]

Where are we on resolution of this issue? I'm willing to help test a beta version of Sencha CMD to try and resolve the issue.