Well I didn't agreed on moving TC binaries to sf or others.
I mentioned that being also involved in projet like Jpackage, I know that's producing ready to use packages is not so easy, expecially when you have to explain to users that they have to get MANY external jars from outside sites.
As Mladen say, the board came mainly from httpd team and in the NATIVE world there is allready distributions which provide the missing/required parts, like openssl, glibc....
But in Java land, there is no REAL distributions (only jpackage for RPM users), and there is a HUGE difference.
Indeed. This move is only thought out in respect to httpd and the related native projects.
I am not. Temporary solutions may last long time. Blocking situations normaly evolve faster.
Yes, what will happen with board if WE decide to stop make Tomcat release until the problem get fixed ?
Bad idea: I think they don't care ;)
Right now, I'm in favor of doing solution A, and removing some of the distributions (the .exe and the embedded dist). It doesn't prevent doing B as well.
I think we should post a statement on the Tomcat website explaning the reasons for the disappearance of the distributions, as well as voicing our opposition (if we indeed all agree we are opposed to this) to the latest board decision.
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
