incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paolo Castagna <>
Subject Re: svn commit: r1200892 - /incubator/jena/README
Date Fri, 11 Nov 2011 15:14:00 GMT
Hi Dennis,
apologies, but I do not understand your issue here.

Probably because I am not a Windows user myself and I am not aware of the
features or lack of features of TortoiseSVN which if I remember correctly
is what you are using.

I would be really surprised if that SVN client does not support a checkout
of a specific directory, SVN as far as I know has been designed for that
use case (i.e. checkout of a directory rather than the entire repository).

The whole Apache SVN repository is just a single repository but no one
would be so 'crazy' to check out the whole entire Apache SVN repo. Isn't
it? (Although, interesting mining activity could be done over a whole
checkout! :-)).

So, if you better explain your problems and what you want to do (and you
can't or fail to do) people here or else where in Apache (or else where)
will be able to help you out.


Dennis E. Hamilton wrote:
> Off-Topic: Until I have run all the cleanups required to upgrade to an SVN 1.7 client
everywhere, it is burdensome to selectively check-out and update pieces of a repo.  I'll do
it then (since there is finer-grained control once I do the upgrade.)
> On-Topic: I am liking this.  It is still the case that an entire repo checkout should
work.  And, for a multi-component project, I favor what is done to tidy the organization into
meaningful sub-projects.
>  - Dennis
> -----Original Message-----
> From: Paolo Castagna [] 
> Sent: Friday, November 11, 2011 06:27
> To:
> Subject: Re: svn commit: r1200892 - /incubator/jena/README
> Yeah! Thanks.
> A proposal for a small addition to this README file:
> """
> The Experimental/ directory contains prototypes which might or might not become 
> supported Jena modules/contributions.
> The Import/ directory contains the Jena CVS and SVN imports from SourceForge, 
> it's here just for historical/archival reasons but we do not expect you to look 
> at it.
> The Scratch/ directory is our little|small|personal playground on the Apache SVN 
> repository, this stuff might or might not made it into Jena code base. A sort of 
> micro Apache Labs ( for tiny things related to Apache 
> Jena. Some of us use also GitHub for this.
> Last but not least, the site/ directory contains the sources for the Apache Jena 
> website and... yes! You can check it out and submit patches for it. Patches on 
> documentation are as welcome as patches for code.
> """
> Feel free to change/improve as you wish.
> The aim is to clearly tell people:
>   - do not waste your time on Import/
>   - you can submit patches for site/ and they are welcome!
>   - if you are curious and not afraid to experiment, feel free to look at
>     Experimental/ and/or Scratch/ but, please, be aware that this is
>     "unsupported" and "unreleased" stuff until it's moved elsewhere.
> Paolo
> wrote:
>> Author: andy
>> Date: Fri Nov 11 14:06:13 2011
>> New Revision: 1200892
>> URL:
>> Log:
>> Add a README for the Jena svn repository
>> Added:
>>     incubator/jena/README
>> Added: incubator/jena/README
>> URL:
>> ==============================================================================
>> --- incubator/jena/README (added)
>> +++ incubator/jena/README Fri Nov 11 14:06:13 2011
>> @@ -0,0 +1,18 @@
>> +Jena README
>> +===========
>> +
>> +Welcome to Apache Jena,  a Java framework 
>> +for writing Semantic Web applications.
>> +
>> +The Jena Framework includes:
>> +
>> ++ an API for reading, processing and writing RDF data in XML, N-triples and Turtle
>> ++ an ontology API for handling OWL and RDFS ontologies;
>> ++ a rule-based inference engine for reasoning with RDF and OWL data sources;
>> ++ stores to allow large numbers of RDF triples to be efficiently stored on disk;
>> ++ a query engine compliant with the latest SPARQL specification
>> ++ servers to allow RDF data to be published to other applications using SPARQL
>> +
>> +The codebase for the active modules is to be found under:
>> +
>> +

View raw message