Not necessarily...
mongrel/branches/stable_1-1 eweaver$ ack 1.1.2
ext/http11_java/org/jruby/mongrel/Http11.java
218:
req.aset(runtime.newString("SERVER_SOFTWARE"),runtime.newString("Mongrel
1.1.2"));
lib/mongrel/const.rb
68: MONGREL_VERSION="1.1.2".freeze
I think someone (you?) forgot to commit the version change. I had to
re-release the gem to fix the daemons dependency problem (due to the
FORCE_PURE thing you added, which I committed a fix for).
Either that or somehow I accidentally reversed your change. I'll patch
things up regardless.
Evan
On Jan 1, 2008 8:46 PM, Luis Lavena <[EMAIL PROTECTED]> wrote:
> On Jan 1, 2008 4:50 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> > I can reproduce. Can you file a ticket?
> >
>
> Then that means rubyforge picked the older file before we replaced
> with the correct one.
>
> That means Tom Copeland is lying! ;-)
> (about how gems the replicated into the mirrors) :-)
>
> Maybe we should fill a ticket on Rubyforge support?
>
> --
>
> Luis Lavena
> Multimedia systems
> -
> A common mistake that people make when trying to design
> something completely foolproof is to underestimate
> the ingenuity of complete fools.
> Douglas Adams
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
