Chris Kimpton wrote:
>Hi,
>
>--- [EMAIL PROTECTED] wrote:
>
>>Quoting Santiago Gala <[EMAIL PROTECTED]>:
>>
>>>David Sean Taylor wrote:
>>>
>>>>I have no problem with it, but didn't Raphael recently making a
>>>>
>>patch
>>
>>>to
>>>
>>>>Turbine for JSPs to work in Jetspeed?
>>>>Does 2.2b1 have Raphael's patch for JSPs?
>>>>Are there any other known issues with 2.2b1 and Jetspeed?
>>>>
>>>I think 2.2b1 has the patch, but Raphael was waiting for velocity
>>>
>>to
>>
>>>have the patches also. He should answer to this one. I think we
>>>
>>can
>>
>>>update (maybe Chris can just try replacing jars and have turbine
>>>modified in the working copy) but Raphael should speak first
>>>
>>about
>>
>>>upgrading. I CC: him to make sure he knows about this one.
>>>
>>the patch is checked in in the turbine-2 repository (2.2b1-dev)
>>i don't know if the velocity stuff is checked in ..
>>there will be a official turbine-2.2b1 soon (i only need to setup
>>my linux box
>>;-)
>>
>
>Can the turbine jar be upgraded - or are we waiting for the
>velocity/turbine release to be official ?
>
[sgala@patusan lib]$ cvs log turbine-2.2b1.jar
RCS file: /home/cvs/jakarta-jetspeed/lib/turbine-2.2b1.jar,v
Working file: turbine-2.2b1.jar
head: 1.1
branch:
locks: strict
access list:
symbolic names:
keyword substitution: b
total revisions: 1; selected revisions: 1
description:
----------------------------
revision 1.1
date: 2001/08/16 15:07:43; author: raphael; state: Exp;
update Turbine and Velocity with patched versions that fix the JSP
inclusion issue, while waiting for these projects to integrate these
patches into their codebase.
=============================================================================
This is the output of cvs log for turbine.jar. Our current file *is*
called turbine-2.2b1.jar, and includes some patches from Raphael. If
anybody can point me to the right jar file *and* the right changelog
comment saying where the jar comes from and where to fetch the exact
source files to reconstruct it, I'll do the update. We will be using
again a jar that will not be easily re-fetchable, so we should provide a
clear tag date and procedure to re-create the sources. One alternative
would be to wait until mpoeschl updates the "official" turbine-2 2.2b1
release. It would be cleaner for me.
In collective development, the ability to reproduce changes and to track
versions is completely essential to avoid driving madness into the
developer/user communities.
I see there are reasons to update the jar, but I have been very confused
by the fact that our jar *is* already called turbine-2.2b1.jar. I
thought the change was already done.
>
>The reason for this patch is that it allows jetspeed to work with the
>Jetty servlet engine under IE. Without it - jetspeed does not work
>on Jetty.
>
>Thanks,
>Chris
>
>=====
>Need somewhere to Live in London - http://freeflats.com
>
>__________________________________________________
>Do You Yahoo!?
>Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
>http://im.yahoo.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
