ingo schuster wrote:
>
> At 20:03 2000-12-11, [EMAIL PROTECTED] wrote:
> >David Sean Taylor wrote:
> > >
> > > Raphael,
> > >
> > > I noticed that you updated the turbine.jar.
> > > Ingo recently zipped up the turbine source into /lib/src/turbine.zip
> > when he
> > > checked in turbine.jar.
> > > I was hoping that we would continue to provide the current source for
> > > turbine with the latest jar if its not too much trouble?
> > >
> >
> >Is that *really* useful ?
> >If you insist I may definitely do it but I didn't see it as necessary since
> >it's just a patched version of the current Turbine CVS and as soon as my
> >reosurces patches are integrated in the turbine CVS tree, I'll update again
> >the jar, this time using the
> >
> >turbine-CVS12112000.jar
> >
> >notation so it would easy ffor anybody interested in the source to check
> >the file for this date from the Turbine CVS.
>
> How can you check out the CVS files of a specific date? Didn't know that
> this is possible and that's why I put the turbine.zip in CVS.
>
It SHOULD be cvs checkout -D YYYY:MM:DD module, BUT I think there is bug
in cvs. Instead, you can do:
cvs checkout module
cvs update -D YYYY:MM:DD -d -P
to "rewind" it back to the given date. Instead, you can use "-r <tag>"
to rewind to a given branch/release tag.
Notice that the date and release features are sticky, i.e. you will need
to do a
cvs update -a -d -P to revert to the HEAD. Notice also -d (create new
directories) and -P (prune empty directories) are very useful to have a
cleaner tree.
CVS is an amazing world of conventions and features, some of those
rather cryptic. But it pays to study the docs a little bit :-)
> >Yes, I know that this introduce again version number in the jar contained
> >in the lib/ directory but now that we have WAR support and everything is
> >automatically configured, I don't see it as an issue.
> >
> > > Thanks for updating the Hypersonic SQL database with the latest Turbine
> > > schema.
> > > Its been broken for the last week or so.
> > > Did you have trouble getting the turbine-hypersonic.sql script to run?
> > > I noticed that you didn't check it in. I had problems with the 'default -1'
> > > on the TURBINE_SCHEDULED_JOB table and had to remove the 'default'
> > > constraints. (Im not sure how SQL-2 compliant hypersonic is, but regardless
> > > Im really beginning to like it.) It now seems obvious to me that
> > > jetspeed.script was used to create the database for the WAR distribution.
> > >
> >
> >Yes I had issues with the unique constraints and the default values but since
> >I hadn't updated hsql.jar for a long time I didn't know if it was related to
> >my jar file or a bug in the sql script. Once I'll know for sure, either I'll
> >notify Jason so that he can fix the torque generation files or I'll update
> >the db.
> >
> > > To point out another point that may or may not be obvious, it appears that
> > > the 'jetspeed-system' directory will no longer be used. Now the default
> > > hypersonic database, cache and logs are all placed under the webapp/WEB-INF
> > > directory.
> > >
> >
> >Yes, I think the WAR deprecates the need for jetspeed-system but I did not
> >modify the conf files in src/config/ on purpose.
> >I'll sync everything when the WAR is building, running and stable.
> >For now, you should consider the WAR building as experimental but committed in
> >the head so that everybody can have a say in what's going in.
> >For now, if you want to have a look at what JR.p and TR.p I use,
> >check /webapp/WEB-INF/conf/
> >
> >BTW, I was considering to remove the Cocoon portlets from the default
> >jetspeed-config.jcfg (and default WAR operation) and only provide the
> >XSP functionality as a "configure yourself" portlet with the help of a
> >few examples.
> >
> >Why ?
> >Because we won't have to distribute cocoon anymore with Jetspeed thus
> >removing a build and distribution dependency
> >Beccause the Cocoon support is a hell to maintain properly and generates
> >at least half the user questions
> >Because templated portlets will remove a lot from XSP support interest
> >Because Cocoon 1.8 is not actively developped anymore so it's an
> >evolutionary dead-end anyway without a serious reimplementation. We might
> >as well not promote too heavily a component which will need a complete
> >overhaul in the near future.
> >
> >I short my opinion is that it's better not to integrate with cocoon and
> >provide a good alternate system ( JSP, velocity, XSL templates portlets)
> >rather than badly integrate with such a cool project.
>
> +1, that's my opinion as well.
+1. See that Leon has added a new XSLT service to Turbine today.
>
> >--
> >Rapha�l Luta - [EMAIL PROTECTED]
> >
> >
> >--
> >--------------------------------------------------------------
> >Please read the FAQ! <http://java.apache.org/faq/>
> >To subscribe: [EMAIL PROTECTED]
> >To unsubscribe: [EMAIL PROTECTED]
> >Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
> >Problems?: [EMAIL PROTECTED]
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
