I am using NewGem and RubiGen for a project of mine that has two
stages. The first is Capistrano-like function where you run an
executable, in this case lockdown. This adds a couple of files into
your project...all is good.
The second (optional) stage is a generate script that installs
models,controllers, views ... etc... I'm testing this script and the
first thing I got was a:
uninitialized constant RubiGen message.
So, I tried the script/generate install_rubigen_scripts and received
the same message.
So, what did I miss. I wouldn't be asking if the
install_rubigen_scripts hadn't returned the same message.
On Sat, Apr 26, 2008 at 12:56 AM, andy <stoneli...@gmail.com> wrote:
> I am using NewGem and RubiGen for a project of mine that has two > stages. The first is Capistrano-like function where you run an > executable, in this case lockdown. This adds a couple of files into > your project...all is good.
> The second (optional) stage is a generate script that installs > models,controllers, views ... etc... I'm testing this script and the > first thing I got was a:
> uninitialized constant RubiGen message.
> So, I tried the script/generate install_rubigen_scripts and received > the same message.
> So, what did I miss. I wouldn't be asking if the > install_rubigen_scripts hadn't returned the same message.
> Let me know what other info you need.
> thanks, > andy
-- Dr Nic Williams http://drnicacademy.com - Ruby/Rails training/dev around the world http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0 (skype) nicwilliams (p) +61 412 002 126 / +61 7 3113 3033 (mail) PO Box 583 Ashgrove 4060 QLD Aus
and see if having just one gem version helps. I say this because I had a funny issue when I had 1.2.4 + 1.3 installed. I have no idea why I had issues, but when I cleaned out my gem cache it fixed it. This isn't a solution, but I'm just interested if it does solve your issue. I'm guessing lots of ppl will have this issue (whatever it is) so it needs to be fixed.
Nic
On Sat, Apr 26, 2008 at 7:07 AM, Nic Williams <drnicwilli...@gmail.com> wrote:
> Hmm, I just released a new rubigen version; perhaps this is the issue, > What version(s) of rubigen + newgem do you have installed?
> $ gem list rubigen > $ gem list newgem
> On Sat, Apr 26, 2008 at 12:56 AM, andy <stoneli...@gmail.com> wrote:
> > I am using NewGem and RubiGen for a project of mine that has two > > stages. The first is Capistrano-like function where you run an > > executable, in this case lockdown. This adds a couple of files into > > your project...all is good.
> > The second (optional) stage is a generate script that installs > > models,controllers, views ... etc... I'm testing this script and the > > first thing I got was a:
> > uninitialized constant RubiGen message.
> > So, I tried the script/generate install_rubigen_scripts and received > > the same message.
> > So, what did I miss. I wouldn't be asking if the > > install_rubigen_scripts hadn't returned the same message.
> > Let me know what other info you need.
> > thanks, > > andy
> -- > Dr Nic Williams > http://drnicacademy.com - Ruby/Rails training/dev around the world > http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0 > (skype) nicwilliams > (p) +61 412 002 126 / +61 7 3113 3033 > (mail) PO Box 583 Ashgrove 4060 QLD Aus
-- Dr Nic Williams http://drnicacademy.com - Ruby/Rails training/dev around the world http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0 (skype) nicwilliams (p) +61 412 002 126 / +61 7 3113 3033 (mail) PO Box 583 Ashgrove 4060 QLD Aus
It looks like the new version corrected the issue. The original issue was that the code generated by the component generator (for Rails) utilized the RubiGen::Base class instead of Rails::Generator::Base. I didn't know any better at the time...the Rails code requires it's generators to be descendants of Rails::Generator::Base.
Anyway...issue resolved. Thanks for Newgem and Rubigen, it has been a really big help.
> It looks like the new version corrected the issue. The original issue was > that the code generated by the component generator (for Rails) utilized the > RubiGen::Base class instead of Rails::Generator::Base. I didn't know any > better at the time...the Rails code requires it's generators to be > descendants of Rails::Generator::Base.
> Anyway...issue resolved. Thanks for Newgem and Rubigen, it has been a > really big help.
> -- > Andrew Stone
-- Dr Nic Williams http://drnicacademy.com - Ruby/Rails training/dev around the world http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0 (skype) nicwilliams (p) +61 412 002 126 / +61 7 3113 3033 (mail) PO Box 583 Ashgrove 4060 QLD Aus
On Fri, Apr 25, 2008 at 6:40 PM, Nic Williams <drnicwilli...@gmail.com> wrote:
> Yeah the 1.3.1 fixes the issues with creating + testing rails generators. > Tis good fun :)
Quick question... any chance of adding in the copy_dirs and copy_files methods Merb uses into Rubigen? Those are some nice additions I think. I don't know if you know about them...they are defined in merb-gen/lib/merb-gen/helpers.rb
On Sat, Apr 26, 2008 at 8:54 AM, Andrew Stone <stoneli...@gmail.com> wrote:
> On Fri, Apr 25, 2008 at 6:40 PM, Nic Williams <drnicwilli...@gmail.com> > wrote:
> > Yeah the 1.3.1 fixes the issues with creating + testing rails > > generators. Tis good fun :)
> Quick question... any chance of adding in the copy_dirs and copy_files > methods Merb uses into Rubigen? Those are some nice additions I think. I > don't know if you know about them...they are defined in > merb-gen/lib/merb-gen/helpers.rb
> -- > Andrew Stone
-- Dr Nic Williams http://drnicacademy.com - Ruby/Rails training/dev around the world http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0 (skype) nicwilliams (p) +61 412 002 126 / +61 7 3113 3033 (mail) PO Box 583 Ashgrove 4060 QLD Aus
I am experiencing the same error whenever I run "script/generate
scaffold" and can't figure out how to fix it. Because I am totally new
to rails, I don't know which gems are relevant, so I'm just going to
list all that I have installed:
I have already tried uninstalling and reinstalling rubigen. I also had
the same issue when using rails 2.1. Again, for the sake of being
thorough, here's an example of what happens:
> > It looks like the new version corrected the issue. The original issue was
> > that the code generated by the component generator (for Rails) utilized the
> > RubiGen::Base class instead of Rails::Generator::Base. I didn't know any
> > better at the time...the Rails code requires it's generators to be
> > descendants of Rails::Generator::Base.
> > Anyway...issue resolved. Thanks for Newgem and Rubigen, it has been a
> > really big help.
> > --
> > Andrew Stone
> --
> Dr Nic Williamshttp://drnicacademy.com- Ruby/Rails training/dev around the worldhttp://drnicwilliams.com- Ruby/Rails/Javascript/Web2.0
> (skype) nicwilliams
> (p) +61 412 002 126 / +61 7 3113 3033
> (mail) PO Box 583 Ashgrove 4060 QLD Aus
In response to my post a few minutes ago about encountering the
"uninitialized constant RubiGen" error:
It's working now. All I had to do was uninstall sproutcore and the
related executables (sc-build, sc-gen, sc-server, sproutcore). I'll
have to tell the sproutcore folks about this. Though my issue has been
resolved, I encourage you to display my posts anyway because
sproutcore is very new and others may encounter the same error.
Kevin
On Apr 25, 6:40 pm, "Nic Williams" <drnicwilli...@gmail.com> wrote:
> > It looks like the new version corrected the issue. The original issue was
> > that the code generated by the component generator (for Rails) utilized the
> > RubiGen::Base class instead of Rails::Generator::Base. I didn't know any
> > better at the time...the Rails code requires it's generators to be
> > descendants of Rails::Generator::Base.
> > Anyway...issue resolved. Thanks for Newgem and Rubigen, it has been a
> > really big help.
> > --
> > Andrew Stone
> --
> Dr Nic Williamshttp://drnicacademy.com- Ruby/Rails training/dev around the worldhttp://drnicwilliams.com- Ruby/Rails/Javascript/Web2.0
> (skype) nicwilliams
> (p) +61 412 002 126 / +61 7 3113 3033
> (mail) PO Box 583 Ashgrove 4060 QLD Aus
> In response to my post a few minutes ago about encountering the
> "uninitialized constant RubiGen" error:
> It's working now. All I had to do was uninstall sproutcore and the
> related executables (sc-build, sc-gen, sc-server, sproutcore). I'll
> have to tell the sproutcore folks about this. Though my issue has been
> resolved, I encourage you to display my posts anyway because
> sproutcore is very new and others may encounter the same error.
> Kevin
> On Apr 25, 6:40 pm, "Nic Williams" <drnicwilli...@gmail.com> wrote:
> > Yeah the 1.3.1 fixes the issues with creating + testing rails generators.
> > Tis good fun :)
> > On Sat, Apr 26, 2008 at 8:39 AM, Andrew Stone <stoneli...@gmail.com> wrote:
> > > On Fri, Apr 25, 2008 at 5:10 PM, Nic Williams <drnicwilli...@gmail.com>
> > > wrote:
> > > > Ooh, sorry didn't see your 2nd email.
> > > > Can you try the following:
> > > It looks like the new version corrected the issue. The original issue was
> > > that the code generated by the component generator (for Rails) utilized the
> > > RubiGen::Base class instead of Rails::Generator::Base. I didn't know any
> > > better at the time...the Rails code requires it's generators to be
> > > descendants of Rails::Generator::Base.
> > > Anyway...issue resolved. Thanks for Newgem and Rubigen, it has been a
> > > really big help.
> Please make public because I have sproutcore also and suddenly I
> cannot even script/generate model where in the past I can...
> having this error "uninitialized constant RubiGen" and scratch my
> head... I will try uninstall sproutcore and see what is the outcome.
> mech
> On Jun 17, 5:01 am, Kevin D <kevin.d...@gmail.com> wrote:
> > In response to my post a few minutes ago about encountering the
> > "uninitialized constant RubiGen" error:
> > It's working now. All I had to do was uninstall sproutcore and the
> > related executables (sc-build, sc-gen, sc-server, sproutcore). I'll
> > have to tell the sproutcore folks about this. Though my issue has been
> > resolved, I encourage you to display my posts anyway because
> > sproutcore is very new and others may encounter the same error.
> > > > It looks like the new version corrected the issue. The original issue was
> > > > that the code generated by the component generator (for Rails) utilized the
> > > > RubiGen::Base class instead of Rails::Generator::Base. I didn't know any
> > > > better at the time...the Rails code requires it's generators to be
> > > > descendants of Rails::Generator::Base.
> > > > Anyway...issue resolved. Thanks for Newgem and Rubigen, it has been a
> > > > really big help.
|
