No "window manager" after building v7.17.1-RC1

[tran...@gmail.com]

Does anyone know what might cause there to be no "window manager" in the build version of the 7.17.1-RC1 release?  When I run the pre-built .zip version, I see the title bar "Ozone Widget Framework" and all of the related buttons, but when I run my "build" version, there doesn't seem to be anything managing the items.  I'm using a CentOS 6.8 VM running a JDK 1.7 with all of the related tools using versions specified in the build manual.  Can anyone help me?  Thanks. 

Matt

[Ross Pokorny]

Could you clarify what exactly you're seeing? Are you saying that the OWF UI
is failing to render? Is it partially rendering or not at all? Are there any
errors in the browser dev tools?

You mention that you built OWF yourself - what steps did you take to do so?

Ross Pokorny

[tran...@gmail.com]

I was using instructions found in the OWF Build Instructions document found in the owf-omp-docs github repo.  I installed the relevant toolset (ant, grails, groovy, etc) and versions and it built well enough, but something's obviously amiss if I'm not seeing any sort of "window manager"

Matt

[Ross Pokorny]

Matt

When you say you aren't seeing any sort of "window manager", I'm still not
clear on _precisely_ what you mean by that. Please send a screenshot of your
browser window showing the issue. Also please confirm whether or not there
are errors printed in your browser's development tools.

Additionally, it may be helpful for you to state which browser (including
version) you are using.

Ross

[tran...@gmail.com]

I'm attaching two screengrabs for comparison, PreBuiltOWF.jpg for the pre-built version that came in the ZIP file, and BuiltFromScratch.jpg that I made from the OWF-bundle-7.17.1-RC1 tarball.  I've also included a zipped log of the build.  I didn't see any obvious errors, but I don't know what to look for.

Matt

[Ross Pokorny]

OK, what you're seeing is OWF without any stylesheets loaded. This usually
means that the CSS compilation during the build failed. Unfortunately that
part of the build is not set up to fail the whole build if the CSS compilation
fails. Looking in your build log, I see the following which confirms this
theory:

_compile-themes-in-war:
[exec] Current OS is Linux
[exec] Executing 'sh' with arguments:
[exec] 'compile_all_themes.sh'
[exec] '--force'
[exec]
[exec] The ' characters around the executable and arguments are
[exec] not part of the command.
[exec] DEPRECATION WARNING:
[exec] Sass 3.5 will no longer support Ruby 1.8.7.
[exec] Please upgrade to Ruby 2.0.0 or greater as soon as possible.
[exec]
[exec] /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require': no such file to load -- sass/script/node (LoadError)
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/lib/compass/
sass_extensions/monkey_patches/browser_support.rb:1
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/lib/compass/
sass_extensions/monkey_patches.rb:2
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/lib/compass/
sass_extensions/monkey_patches.rb:1:in `each'
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/lib/compass/
sass_extensions/monkey_patches.rb:1
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/lib/compass/
sass_extensions.rb:9
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/lib/compass.rb:5
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/lib/compass.rb:
4:in `each'
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/lib/compass.rb:4
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
[exec] from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/bin/compass:20
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/bin/compass:8:in
`fallback_load_path'
[exec] from /usr/lib/ruby/gems/1.8/gems/compass-0.11.7/bin/compass:19
[exec] from /usr/bin/compass:19:in `load'
[exec] from /usr/bin/compass:19
[antcall] Exiting /home/mclark/Code/Ozone/owf-framework-7.17.1-RC1/
build.xml.

The CSS compilation depends on the ruby tools sass and compass. I would check
that you have those two tools, along with ruby itself, installed with the
correct versions as described in the build doc. In particular, it looks like
you have the right version of compass, the wrong version of ruby (which may or
may not matter) and possibly no version of sass at all. When you have all
three tools installed correctly you should be able to run ruby --version,
compass --version, and sass --version and see the correct version of each get
printed out.

For convenience, here are the correct versions of those three tools as listed
in the build guide (for OWF 7.17):

ruby 1.9.2
compass 0.11.7
sass 3.1.3


Ross Pokorny

[tran...@gmail.com]

Ross, 

After a bit of bludgeoning, I got all versions set up, but found out compass removed the "blueprint" theme from the core.  I had to add the compass-blueprint (1.0.0) gem to get everything working.  But it does now.  Thanks for the help.  

Matt