Please help! Getting file not found error running Sass and Compass as jar in ant
axyl
our build process. I used the following tutorial to add compass as a
target in ant: http://caueguerra.com/tutorial-using-sass-in-a-java-project
Here are the gems in my uber-jar containing jruby:
> java -jar jruby-compass-gems.jar -S gem list
*** LOCAL GEMS ***
chunky_png (1.2.5)
compass (0.11.5)
fssm (0.2.7)
rake (0.8.7)
sass (3.1.1)
sources (0.0.1)
Here is my ant target for calling compass compile, just simpler than
the tutorial so I can put all files in one place:
<project name="run-compass" basedir=".">
<property name="apps.root" value="${basedir}/src/main/webapp/
apps" />
<property name="sass.dir" value="${apps.root}/resources/sass" />
<!-- Include jruby-compass jar -->
<path id="jruby.classpath">
<fileset dir="${basedir}">
<include name="jruby*.jar"/>
</fileset>
</path>
<target name="compile.sass">
<java classname="org.jruby.Main" fork="true" failonerror="true"
classpathref="jruby.classpath">
<arg line="${basedir}/compile.rb ${basedir} compile $
{sass.dir}"/>
</java>
</target>
</project>
With below modifications to compile.rb:
# Instead of loading lib dirs, just add the first arg
# Dir.entries(ARGV[0]).each do |lib|
# $LOAD_PATH.unshift "#{ARGV[0]}/#{lib}/lib"
#end
$LOAD_PATH.unshift "#{ARGV[0]}"
require 'rubygems'
require 'compass'
require 'compass/exec'
# select_appropriate_command_line_ui is no longer a valid method, so
don't use
#command_line_class =
Compass::Exec::Helpers.select_appropriate_command_line_ui [ARGV[1],
ARGV[2], "-q"]
exit Compass::Exec::SubCommandUI.new([ARGV[1], ARGV[2], "-q"]).run!
I see this error in the generated .css file after running ant:
Syntax error: File to import not found or unreadable: shared.
Load paths:
C:\Users\aliu\workspace\ui/src/main/webapp/apps/
resources/sass
file:C:/Users/aliu/workspace/ui/jruby-compass-
gems.jar!/gems/compass-0.11.5/frameworks/blueprint/stylesheets
file:C:/Users/aliu/workspace/ui/jruby-compass-
gems.jar!/gems/compass-0.11.5/frameworks/compass/stylesheets
C:/Users/aliu/workspace/ui/src/main/webapp/apps/
resources/sass/../../../lib/ext-4.0.7/resources/themes/stylesheets
Compass::SpriteImporter
on line 1 of file:C:/Users/aliu/workspace/ui/jruby-compass-
gems.jar!/gems/compass-0.11.5/frameworks/compass/stylesheets/compass/
css3/_border-radius.scss
from line 1 of file:C:/Users/aliu/workspace/ui/jruby-compass-
gems.jar!/gems/compass-0.11.5/frameworks/compass/stylesheets/compass/
_css3.scss
The offending line in _border-radius.scss is:
@import "shared";
Notice the load path contains compass stylesheets. I find it really
strange that compass was able to find _border-radius.scss, but not
_shared.scss, because they're in the same directory. I checked the jar
content to make sure _shared.scss exists. I tested running compile.rb
in the ${basedir} directly:
compile.rb . compile src\main\webapp\apps\resources\sass
It worked and created the .css file correctly, which means the problem
seems to lie in running from ant, or maybe jruby. Has anyone
experience something similar, or could give some insight to this
problem? Any suggestion appreciated!
Franz Heidl
generally fail when referencing a file in the exact same directory as
the file that contains the @import directive. We do not have a
solution yet either.
axyl
I was able to discover a workaround, though it's a bit painful. I
realized that while @import "shared" cannot be found, @import "compass/
css3/shared" is okay, so I modified all such local @imports in compass
stylesheets to reference the more absolute paths before packaging
compass up into the jar.
Compass team, is it possible for you to incorporate this workaround?
On Jan 23, 6:00 am, Franz Heidl <lastmodernis...@googlemail.com>
wrote:
Franz Heidl
sorry for getting back so late.
We were considering this option, but having to manually change paths
throughout Compass turned out not to be an option when we're headed
towards full build/deployment automation.
What we do now is to extract Compass from out of the .jar at a
relatively early stage of the Maven build so it actually exists in a
directory once the compile is happening, and then all is well and all
the @import directives work just fine!
Probably not an ideal or overly elegenat solution, but it does work
and saves us from the hassle of manually changing paths in all the
Compass files.
If you need any more details on how exactly we do this let me know and
I can try to head one of our devs to this group, I am an Designer/
Frontend Developer and my understanidng of all things build/Maven, etc
is pretty limited I have to admit.
Best,
Franz
cgonzales
I've also been struggling to get compass to run from a jar following
Axyl's modifications to the original tutorial. I get an error that it
can't find compass/reset. I'm also a frontend guy and have been
stumbling my way through Maven build tasks. If you could shared how
you extract Compass from the jar as part of a Maven build I'd
appreciate it.
Thanks,
Chris
On Feb 17, 4:07 am, Franz Heidl <lastmodernis...@googlemail.com>
wrote:
> sorry for getting back so late.
> We were considering this option, but having to manually change paths
>
> What we do now is to extract Compass from out of the .jar at a
> relatively early stage of the Maven build so it actually exists in a
> directory once the compile is happening, and then all is well and all
> the @import directives work just fine!
>