Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

compass command returns with exit status 0 even on errors #432

Closed
epeli opened this Issue Jun 16, 2011 · 4 comments

Comments

Projects
None yet
5 participants

epeli commented Jun 16, 2011

The compass command returns with exit status 0 even if compiling failed. It should return non zero status if even one file fails to compile.

This is for scripting purposes. Exit status is an ideal way to detect errors and notify about them.

This is at least on Compass 0.11.1 (Antares).

Latest Compass version is 0.11.3

epeli commented Jun 16, 2011

No difference on latest Compass.

Owner

scottdavis commented Jun 16, 2011

noted and ill make sure this gets fixed

peritus commented Jun 22, 2011

I want this, so rake fails if there is an error in the .scss source.

@dbussink dbussink pushed a commit to dbussink/compass that referenced this issue Jul 14, 2011

@chriseppstein chriseppstein Merge branch 'stable'
* stable:
  Fix failing test when updating to latest SASS
  Gemfile.lock should not be part of a library / gem
  fix typo
  Fix issue with parent directory references within the sass_path in the compass compiler.
  Version bump.
  Update changelog
  Return a non-zero exit code if there are any stylesheet compilation errors. Closes GH-432.
  Fix test failures.
  Better docs for the shadow mixins. Closes GH-433.
  Include the Compass logger to prevent "uninitialized constant Compass::Logger"
  Broken link fixed to what I think is the correct section of the SASS docs.
  grid-background vertical rhythm should be based off of $blueprint-font-size, rather than a static value.
  :focus should not use shorthand border property, since it only need to change the border-color
  update changelog
  Fix absolute path detection on Windows.
  Fix the mime type returned for svg images. Closes GH-442.

Conflicts:
	Gemfile.lock
6c12749
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment