cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Howard <geoff.how...@gmail.com>
Subject Re: [proposal] Cocoon documentation system
Date Sat, 15 Jan 2005 14:17:10 GMT
On Sat, 15 Jan 2005 09:42:17 +0100, Reinhard Poetz <reinhard@apache.org> wrote:
...
> >>My first goal is
> >>reusing existing functionality (SVN, Forrest, static web pages). Writing
> >>the missing pieces (a small web application to edit docs online) shouldn't
> >>be too difficult - especially using CocoonForms (HTMLArea with HTMLCleaning
> >>convertor are shining here!) and Flowscript.
> >>
> >>At the end of the document you find a roadmap. It also contains some parts
> >>where I *really* need some help by others:
> >>
> >> - component (Java) that reads from and commits to SVN - should work over
> >>   WebDAV, shouldn't it?
> >>   I know there are some specialist in this community who could help out
> >>   here (Unico, Gianugo, Guido)
> >
> > We have a huge team of specialists on the dev list.
> 
> Yep. I hope that I can convince at least one of them to help me. Actually I need
> some Java code ;-) So here I ask officially: Who volunteers to write the Java
> code that communicates with the SVN repository (read and commit)?
 
You may find this more problematic than you'd expect.  I follow the
subclipse list a little and have the impression that pure-java library
development against SVN lags behind because it's difficult to keep up
with the evolving standard.  I should have thought that the rate of
evolution has significantly slowed, but that is not the impression I
get.  Subclipse for instance uses jni for the low level svn operations
so it can go against the original native libraries.

On the other hand, there are some attempts to provide pure java svn
libraries (one is called javaSVN I think?) so if these are usable in
practice, the work could be trivial.

Geoff

Mime
View raw message