A dummy project is a good idea. I'll look into that. The reason I can't just download jars from central is that I'm not in a maven environment at run time. I build a ruby gem with the jars already included, which I do by running 'mvn dependencies'. That requires me to have a pom.xml, hence need for source checkout.
Ian On 12 Sep 2014 11:48, "Andy Seaborne" <[email protected]> wrote: > Including from maven central was my reaction as well. > > Would it work for you to depend on org.apache.jena:jena-tdb ? Or are you > doing something clever as well? Excluding certain jars? > > Or there is the maven artifact "apache-jena-libs" to include as > <type>pom</type>. > > All it has is: > > <dependencies> > <dependency> > <groupId>org.apache.jena</groupId> > <artifactId>jena-tdb</artifactId> > <version>1.1.0-SNAPSHOT</version> > </dependency> > </dependencies> > > so it's the stable "include the main jars" point. > (you could even shade into one uber jar for convenience.) > > Andy > > > > On 12 Sep 2014 11:31, "Stian Soiland-Reyes" < >> [email protected]> wrote: >> >> Any reason why you can't download the Jena jars from the Maven central >>> repository..? >>> On 12 Sep 2014 11:16, "Ian Dickinson" <[email protected]> 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? >>>> >>>> Ian >>>> >>>> >>> >> >
