Closed otobrglez closed 14 years ago
A few things...
I thought that Heroku has a read-only file system meaning that you have to pre-package all your production assets in your repo before pushing...
This actual error seems to be something with Jammit's logging, but I also think that it's having problems finding java on Heroku's servers:
from /home/slugs/273882_5eea37c_5577/mnt/.bundle/gems/ruby/1.8/gems/jammit-0.5.1/lib/jammit.rb:173:in `warn'
from /home/slugs/273882_5eea37c_5577/mnt/.bundle/gems/ruby/1.8/gems/jammit-0.5.1/lib/jammit.rb:161:in `disable_compression'
from /home/slugs/273882_5eea37c_5577/mnt/.bundle/gems/ruby/1.8/gems/jammit-0.5.1/lib/jammit.rb:151:in `check_java_version'
It really seems like you'd want to run jammit before commiting/pushing to heroku...
I am seeing the same issue.
I am getting the same deprecation warning as well running a Rails3 app under Ubuntu against REE (1.8.7p253) and Jammit 0.5.1
I tried Jammit on Ruby 1.9.2-head with Rails 3.0.0. and i'm also getting same errors... After installing Java / JDK everything worked fine... It seams that it trys to give error that Java is not present on system but it uses wrong(deprecated) system for errors/warnings...
heroku cloud does now have Java... And heroku is read-only... So this two facts restrict usage of jammit. But you can still "prepackage" everything with jammit before deployin to jammit (perhapse using different enviroments)
Just specify the below in your Gemfile if you are using Bundler
gem "jammit", :git => "git://github.com/documentcloud/jammit.git"
Hi all!
I want to use Jammit on Heroku cloud... Localy it works great and its perfect!
This is error log from heroku...