With great interest I read about the suggested integration of JavaSVN into
the main subversion tree and applaud it wholeheartedly. I agree with all
that's been said so far but would like to add another view on reducing
complexity and enabling a clean integration of the two. I should probably
add that I know only very little about the dependencies of the various
Subversion layers and whether my suggestion is feasible at all, but I do
know a bit about dependency management, continuous integration and
building Java/JNN stuff, so I'm not purely an armchair advisor. ;)
IMHO it would be great if JavaSVN would completely play the role of the
JavaHL interfaces that can act as 'client' and replace the corresponding
JavaHL client interfaces. Anything that JavaSVN cannot do - e.g.
"server-side" things - can continue to be wrapped on top of native SVN.
While both should ideally be in a single tree, it would be helpful if the
resulting JARs were separate - on without native dependency for easy
IDE/app integration of client-side tasks, the other with the required
native dependency. This would not only enforce consistent builds from a
single source, but also reduce the size, complexity and amount of work
going into the JNI mappings.
Now please go ahead and tell me what a boneheaded idea this is. :-)
Holger
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 3 17:26:43 2005