Re: Toward Jena 3.10.0

This all makes sense to me. We've had a few nice contributions from various non-committer folks; perhaps we could mention them to give some credit? I'd like to give a straight Jira link but that kind of search is beyond my -fu. Here are some examples: https://issues.apache.org/jira/browse/JENA-

[jira] [Resolved] (JENA-1642) Schemagen configuration option "header" throws exception

[ https://issues.apache.org/jira/browse/JENA-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1642. - Resolution: Fixed Assignee: Andy Seaborne Fix Version/s: Jena 3.10.0 > Schemagen c

Re: Module retirement

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

[jira] [Resolved] (JENA-1641) Provide Iter.flatMap

[ https://issues.apache.org/jira/browse/JENA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1641. - Resolution: Done > Provide Iter.flatMap > > > Key: JENA-1641

[jira] [Commented] (JENA-1641) Provide Iter.flatMap

[ https://issues.apache.org/jira/browse/JENA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703517#comment-16703517 ] ASF subversion and git services commented on JENA-1641: --- Commit 7ac6

[jira] [Commented] (JENA-1641) Provide Iter.flatMap

[ https://issues.apache.org/jira/browse/JENA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703520#comment-16703520 ] ASF GitHub Bot commented on JENA-1641: -- Github user asfgit closed the pull request at

[jira] [Commented] (JENA-1642) Schemagen configuration option "header" throws exception

[ https://issues.apache.org/jira/browse/JENA-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703519#comment-16703519 ] ASF subversion and git services commented on JENA-1642: --- Commit 8938

[jira] [Commented] (JENA-1642) Schemagen configuration option "header" throws exception

[ https://issues.apache.org/jira/browse/JENA-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703521#comment-16703521 ] ASF GitHub Bot commented on JENA-1642: -- Github user asfgit closed the pull request at

[jira] [Commented] (JENA-1641) Provide Iter.flatMap

[ https://issues.apache.org/jira/browse/JENA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703518#comment-16703518 ] ASF subversion and git services commented on JENA-1641: --- Commit 4110

[GitHub] jena pull request #499: JENA-1641: Iter.flatMap.

Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/499 ---

[GitHub] jena pull request #500: JENA-1642: Check has value for header instead of is ...

Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/500 ---

[GitHub] jena issue #500: JENA-1642: Check has value for header instead of is true

Github user afs commented on the issue: https://github.com/apache/jena/pull/500 > it appears that the maven tools are no being built as part of the main project. Is that the case? Yes, I'm afraid it is. Some tests fail when used with Apache parent >19 (I just checked with v21

[jira] [Commented] (JENA-1642) Schemagen configuration option "header" throws exception

[ https://issues.apache.org/jira/browse/JENA-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703513#comment-16703513 ] ASF GitHub Bot commented on JENA-1642: -- Github user afs commented on the issue:

Re: Toward Jena 3.10.0

I will have to look into that I guess since I am frequent user of spatial data. why not go to 7.5? was there an incompatibility? On Thu 29. Nov 2018 at 16:53, Andy Seaborne wrote: > Jena 3.1.0 would be around the end of the year. I'd like to make use of > Greg's GeoSPARQL project the "headline"

Toward Jena 3.10.0

Jena 3.1.0 would be around the end of the year. I'd like to make use of Greg's GeoSPARQL project the "headline" item for the release and to retire jena-spatial in 3.10.0 as an indication of this. Because retirement is a new process for the project, I'm sending this first 3.10.0 message quite e

Re: Module retirement

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

Module retirement

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

[jira] [Commented] (JENA-664) GeoSPARQL support for Jena

[ https://issues.apache.org/jira/browse/JENA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703427#comment-16703427 ] Andy Seaborne commented on JENA-664: [jena@dev email message|https://lists.apache.org/