On 12/09/14 13:15, Ian Dickinson wrote:
I'm generally in favour of the move to git, but I have a question. At
the moment, I bake a subset of Jena .jars into my jena-jruby project
(https://rubygems.org/gems/jena-jruby). I do this by svn co'ing the
jena-tdb module, and then getting mvn to download the dependencies
specified in the module's pom.
I don't think it would be appropriate or useful to bake all of Jena
into the project (I could be persuaded otherwise, but Fuseki, for
example, doesn't seem to fit). Git, in my experience, has difficulty
letting you check out just part of the project tree. Any suggestion as
to how I could adapt my approach to work with a gitified Jena?
I understood that the target of the move would be Github. One option
might be to use the svn support in Github, which lets you use SVN tools
to access any github repository:
https://help.github.com/articles/support-for-subversion-clients
Using this, you should be able to check out just a part of the tree via
svn commands.
It's not perfect, but it works for us for some things where native git
is cumbersome.
-Osma
--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Teollisuuskatu 23)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
[email protected]
http://www.nationallibrary.fi
