The answer to my issue is this:
In ./lib/tasks/framework.rake, the entire set of rake task definitions
is wrapped in this conditional
unless File.directory? "#{RAILS_ROOT}/app"
...define :freeze, :unfreeze and friends...
end
and I had an "app" directory under Rails.root.
Anybody know the reasoning behind this?
Wes
On 6/1/11 11:12 PM, Wes Gamble wrote:
On 6/1/11 9:18 PM, Jim Gay wrote:
On Wed, Jun 1, 2011 at 9:50 PM, Paul Noden<[email protected]> wrote:
Wes,
On 1 June 2011 23:58, Wes Gamble<[email protected]> wrote:
My rake -T list now stops after
radiant:import:prototype:stylesheets (no
unfreeze and no update tasks)
A fresh install of a Radiant app. shows all of the Radiant tasks I
expect,
including unfreeze and all of the update subtasks.
I can tell you that I have these appearing in my current project
running on
RC2 which was created on RC1, but can't really help with fixing
broken rake
tasks - I had to abandon a 0.9.1 to RC1 project upgrade for a
rebuild of the
project on RC1 specifically because I couldn't access a vast number
of rake
tasks.
You can install on RC2, import your extensions and leverage the
existing
database, unless you're looking at debugging the issue, I
volunteered to
assist in debugging in my own email but didn't get any interest?
Paul
I want to restate this so I'm sure I get the problem. There are rake
tasks missing when you upgrade from 0.9.1 to an RC. Is that correct?
Paul, I'm not sure I understand, but I missed your offer for
debugging: I accept!
-Jim
Paul saw missing rake tasks when upgrading from 0.9.1 to 1.0.0 RC1.
I installed RC2 "over" an existing (new) RC1 install, everything was
fine, I even incorporated the rake radiant:update:cached_assets task
into my deploy (which is how I found out about my issue), and then
later in the day, I could no longer see some of my rake tasks.
I will try reinstalling radiant "over" my app again and see if
anything changes.
Wes
