Rails - Apr 2006 - Does anybody know what what is causing this console message?

This started, I think, after I upgraded to 1.1.

trunk 508 $ruby script/console
Loading development environment.
/usr/local/lib/ruby/1.8/test/unit/assertions.rb:265: warning: already 
initialized constant UncaughtThrow
>> 
Everything seems to work in the console, however.

Keith

-- 
Posted via http://www.ruby-forum.com/.

On 4/7/06, Keith Lancaster <klancaster1957@gmail.com>
wrote:
> This started, I think, after I upgraded to 1.1.
>
> trunk 508 $ruby script/console
> Loading development environment.
> /usr/local/lib/ruby/1.8/test/unit/assertions.rb:265: warning: already
> initialized constant UncaughtThrow
> >>
>
> Everything seems to work in the console, however.
One result on Google makes it look as though engines may be involved:
<http://permalink.gmane.org/gmane.comp.lang.ruby.rails.engines.user/483>.
> Keith
Sincerely,

Tom Lieber
http://AllTom.com/
http://GadgetLife.org/

Yeah - we''re looking into this.

- james

On 4/17/06, Tom Lieber <alltom@gmail.com> wrote:
> On 4/7/06, Keith Lancaster <klancaster1957@gmail.com> wrote:
> > This started, I think, after I upgraded to 1.1.
> >
> > trunk 508 $ruby script/console
> > Loading development environment.
> > /usr/local/lib/ruby/1.8/test/unit/assertions.rb:265: warning: already
> > initialized constant UncaughtThrow
> > >>
> >
> > Everything seems to work in the console, however.
>
> One result on Google makes it look as though engines may be involved:
>
<http://permalink.gmane.org/gmane.comp.lang.ruby.rails.engines.user/483>.
>
> > Keith
>
> Sincerely,
>
> Tom Lieber
> http://AllTom.com/
> http://GadgetLife.org/
>
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
>

--
* J *
  ~