On Thu, 2011-09-08 at 22:24 +0100, Andy Seaborne wrote: > > > > > -------- Original Message -------- > > Subject: Re: Starting fuseki from a configuration file > > Date: Thu, 08 Sep 2011 20:56:59 +0100 > > From: Paolo Castagna <[email protected]> > > Reply-To: [email protected] > > To: [email protected] > > > > Dave Reynolds wrote: > >> On Thu, 2011-09-08 at 17:13 +0100, Chris Clarke wrote: > >>> Hi all, > >>> > >>> I'm struggling to get fuseki to start and read config from a > >>> configuration file (as documented at > >>> http://openjena.org/wiki/Fuseki#Running_a_Fuseki_Server and > >>> http://openjena.org/wiki/Fuseki#Fuseki_Configuration_File) > >>> > >>> I'm doing: > >>> > >>> $ svn co http://jena.svn.sourceforge.net/svnroot/jena/Fuseki/trunk fuseki > >> > >> Fuseki, like all the Jena modules, is now maintained in the Apache > >> infrastructure: > >> https://svn.apache.org/repos/asf/incubator/jena/Jena2/Fuseki > > > > By the way, this happened to me as well a couple of times (browsers cache > > URLs). > > > > Maybe we could delete stuff in SourceForge (history will remain anyway) and > > replace it with just a README.txt file with the message "moved here...". > > This is what I usually do (for example: https://github.com/castagna/LARQ) to > > avoid these problems. History is always there: > > https://github.com/castagna/LARQ/commits/master > > > > Paolo > > +1
+1 > This is a signficant step so I suggest we need project consensus by the > 3 day rule, including discussion of alternatives. Are there other ways > of tombstoning to consider? I'd also be OK with Paolo's alternative of just deleting the build files (and adding a MOVED/README). Less effective but does make history browsing easier. Dave
