Frank, Their was a patch to Turbine required by Jetspeed that was not committed at the time the jar file was placed in Jetspeed's CVS. I believe the turbine patch has since been committed. I have request another Turbine patch. When that one is committed, I will update Turbine.jar.
As a general rule you can use the -D flag on the CVS checkout command to get the source as of the date specified, the date in this case is 23-Nov-2001. Thus their is no need to maintain the turbine source code in Jetspeed. In this case, you could argue the path to turbine should be in Jetspeed's CVS Paul Spencer Frank T. Villarreal, Jr. wrote: > Hello All! > > I am attempting custom modifications to Jetspeed and by default Turbine > code. I noticed that the lastest "release" of Jetspeed utilizes > turbine-2.2b1-20011123.jar. When I go to retrieve Turbine's source from CVS > ... I'm getting Turbine's HEAD code ... does anyone know the CVS module name > for the Turbine source code associated with the aforementioned jar ... I > would like to make sure my Turbine modifications are in sync with the > Jetspeed release's source code since they are inter-dependant. Please tell > me there is a snapshot module of the source code for that jar ... or am I > out of luck? If I am out of luck, can I make a humble suggestion? In future > releases of Jetspeed, can we make sure there is a CVS Turbine source code > module available for the jar that is included with Jetspeed? Just a thought > ... it would probably save a lot of headaches for developers trying to > modifiy the code. Anyway, thanks for any help! > > -Frank > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
