On Jan 2, 2008 2:34 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> 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.
Damn, I did it, but as you said, forgot the commit (maybe is in my WC
at office).
> 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).
Please excuse Evan this took you time away from your life (since is
January 1st of a new year!).
I think part of the problem was the urgent need to release a new
version with the proper fix, neglecting things like that.
For what matters, we could alter the extconf.rb to use a define and
get the proper version build inside the http11 extension.
Currently I'm doing something like that for mongrel_service.
> Either that or somehow I accidentally reversed your change. I'll patch
> things up regardless.
>
Again, thank you Evan.
Have a nice week and talk soon.
--
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
