jena-fuseki1 and jena-csv code retired.
You can delete the target/ directoru in each area after the git pull to
free on that disk space.
Andy
On 13/12/2018 11:50, Andy Seaborne wrote:
We can send a message to users@ to alert them to the upcoming changes.
spatial is still in discussion.
We can send a message to users@ to alert them to the upcoming changes.
spatial is still in discussion.
SDB and jena-maven-tools (move command line schemagen to jena-cmds) are
also potential retirements, but not in the 3.10.0 timeframe.
Are there any other modules to put on the list to attract
Sorry for the noise, but I just realized that I said the opposite of what I
meant to!
>> My only concern is that we should do it before people have a chance to fork
should have read,
> My only concern is that we should do it AFTER people have a chance to fork
ajs6f
> On Nov 29, 2018, at 11:4
I'd prefer (2). It's clean and it _uses_ VC instead of working around it.
My only concern is that we should do it before people have a chance to fork,
because they'll want to do that as late as possible. But we can ameliorate that
by just making a couple of loud announcements first. We might wan
Let's retire some modules:
jena-spatial [+]
jena-fuseki1
jena-csv
by not including them in the next release; they should all work but
there isn't a way to signal "deprecation" other than by talking about it
(which we've done) and doing it.
There are several ways to go about this.
1/ have an
