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-1642 https://issues.apache.org/jira/browse/JENA-1606 ajs6f > On Nov 29, 2018, at 11:44 AM, 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" 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 early to give us discussion time. > > == Retirements > > We have talked about this before but not actually done anything. See separate > thread for discussion on retirement process and for the first modules: > > jena-spatial > jena-fuseki1 > jena-csv > > == Headlines > > JENA-664 : GeoSPARQL support > > 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. > > JENA-1621 : Lucene upgrade to 7.4 > May need to reload lucene indexes. > (e.g. the lucene index was create originally with Lucene v5.x (prior Jena > 3.3.0). See Lucene upgrade tool. > https://lucene.apache.org/solr/guide/7_4/indexupgrader-tool.html > > JENA-1623 : Fuseki security > JENA-1627 : HTTP support > https://issues.apache.org/jira/browse/JENA-1623 > http://jena.staging.apache.org/documentation/fuseki2/data-access-control > > == JIRA: > > 31 currently. > > https://s.apache.org/jena-3.10.0-jira > > == Updates > > Only plugins. JENA-1624 > > surefire : 2.21.0 -> 2.22.1 (+ SUREFIRE-1588) > compiler : 3.7.0 -> 3.8.0 > shade: 3.1.0 -> 3.2.0 > > Andy
[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 configuration option "header" throws exception > > > Key: JENA-1642 > URL: https://issues.apache.org/jira/browse/JENA-1642 > Project: Apache Jena > Issue Type: Bug > Components: Jena, Maven Tools >Affects Versions: Jena 3.6.0 >Reporter: Joseph Sarjeant >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.10.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > When using Jena Schemagen from the maven plugin the configuration option for > `header` throws a `BadBooleanException`. Schemagen is checking for `isTrue` > for this option while the value specified is intended to be a String. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
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:48 AM, ajs6f wrote: > > 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 want also > to make a point of pointing at replacements, even if they seem obvious to us. > > ajs6f > >> On Nov 29, 2018, at 11:45 AM, Andy Seaborne wrote: >> >> 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 area "archived/" with the modules moved there. >> This leaves them in the source-release and browsable in git. >> >> 2/ Delete from git. Maybe leave a file somewhere to record the commit ids. >> >> 3/ A new separate git-repo for "jena-misc" >> https://git-wip-us.apache.org/repos/asf/jena-misc.asf >> (or use gitbox and put it on github mirroed back to ASF.) >> >> and maybe some others. >> >> I think (1) is not definite enough. >> >> Thoughts/suggestions/... >> >> Andy >> >> [+] >> jena-spatial :: this is in jena-fuseki-webapp >> [INFO] +- org.apache.jena:jena-spatial:jar:3.10.0-SNAPSHOT:compile >> [INFO] | +- org.apache.lucene:lucene-spatial:jar:7.4.0:compile >> [INFO] | +- org.apache.lucene:lucene-spatial-extras:jar:7.4.0:compile >> [INFO] | | +- org.apache.lucene:lucene-spatial3d:jar:7.4.0:compile >> [INFO] | | \- io.sgr:s2-geometry-library-java:jar:1.0.0:compile >> [INFO] | \- org.locationtech.spatial4j:spatial4j:jar:0.6:compile >
[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
> URL: https://issues.apache.org/jira/browse/JENA-1641
> Project: Apache Jena
> Issue Type: Improvement
>Affects Versions: Jena 3.9.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.10.0
>
>
> This is missing from {{Iter}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1641) Provide Iter.flatMap
[
https://issues.apache.org/jira/browse/JENA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703517#comment-16703517
]
ASF subversion and git services commented on JENA-1641:
---
Commit 7ac69b3ad7e2be3398b9daee72954ffa0efb36c3 in jena's branch
refs/heads/master from [~an...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=7ac69b3 ]
JENA-1641: Iter.flatMap.
> Provide Iter.flatMap
>
>
> Key: JENA-1641
> URL: https://issues.apache.org/jira/browse/JENA-1641
> Project: Apache Jena
> Issue Type: Improvement
>Affects Versions: Jena 3.9.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.10.0
>
>
> This is missing from {{Iter}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1641) Provide Iter.flatMap
[
https://issues.apache.org/jira/browse/JENA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703520#comment-16703520
]
ASF GitHub Bot commented on JENA-1641:
--
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/499
> Provide Iter.flatMap
>
>
> Key: JENA-1641
> URL: https://issues.apache.org/jira/browse/JENA-1641
> Project: Apache Jena
> Issue Type: Improvement
>Affects Versions: Jena 3.9.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.10.0
>
>
> This is missing from {{Iter}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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=16703519#comment-16703519 ] ASF subversion and git services commented on JENA-1642: --- Commit 8938fc9b353d2c815c306b787cbfe08a612e213a in jena's branch refs/heads/master from [~an...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=8938fc9 ] JENA-1642: Merge commit 'refs/pull/500/head' of https://github.com/apache/jena This closes #500. > Schemagen configuration option "header" throws exception > > > Key: JENA-1642 > URL: https://issues.apache.org/jira/browse/JENA-1642 > Project: Apache Jena > Issue Type: Bug > Components: Jena, Maven Tools >Affects Versions: Jena 3.6.0 >Reporter: Joseph Sarjeant >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > When using Jena Schemagen from the maven plugin the configuration option for > `header` throws a `BadBooleanException`. Schemagen is checking for `isTrue` > for this option while the value specified is intended to be a String. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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=16703521#comment-16703521 ] ASF GitHub Bot commented on JENA-1642: -- Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/500 > Schemagen configuration option "header" throws exception > > > Key: JENA-1642 > URL: https://issues.apache.org/jira/browse/JENA-1642 > Project: Apache Jena > Issue Type: Bug > Components: Jena, Maven Tools >Affects Versions: Jena 3.6.0 >Reporter: Joseph Sarjeant >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > When using Jena Schemagen from the maven plugin the configuration option for > `header` throws a `BadBooleanException`. Schemagen is checking for `isTrue` > for this option while the value specified is intended to be a String. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1641) Provide Iter.flatMap
[
https://issues.apache.org/jira/browse/JENA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703518#comment-16703518
]
ASF subversion and git services commented on JENA-1641:
---
Commit 4110a0420d84a2b7e72d8da9d6e70c07e82cc2f9 in jena's branch
refs/heads/master from [~an...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=4110a04 ]
JENA-1641: Merge commit 'refs/pull/499/head' of https://github.com/apache/jena
This closes #499.
> Provide Iter.flatMap
>
>
> Key: JENA-1641
> URL: https://issues.apache.org/jira/browse/JENA-1641
> Project: Apache Jena
> Issue Type: Improvement
>Affects Versions: Jena 3.9.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.10.0
>
>
> This is missing from {{Iter}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 - this is still the case). ``` [ERROR] The following builds failed: [ERROR] * schemagen-integration-1/pom.xml [ERROR] * schemagen-integration-4/pom.xml [ERROR] * schemagen-integration-2/pom.xml [ERROR] * schemagen-integration-0/pom.xml [ERROR] * schemagen-integration-3/pom.xml ``` ---
[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=16703513#comment-16703513 ] ASF GitHub Bot commented on JENA-1642: -- 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 - this is still the case). ``` [ERROR] The following builds failed: [ERROR] * schemagen-integration-1/pom.xml [ERROR] * schemagen-integration-4/pom.xml [ERROR] * schemagen-integration-2/pom.xml [ERROR] * schemagen-integration-0/pom.xml [ERROR] * schemagen-integration-3/pom.xml ``` > Schemagen configuration option "header" throws exception > > > Key: JENA-1642 > URL: https://issues.apache.org/jira/browse/JENA-1642 > Project: Apache Jena > Issue Type: Bug > Components: Jena, Maven Tools >Affects Versions: Jena 3.6.0 >Reporter: Joseph Sarjeant >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > When using Jena Schemagen from the maven plugin the configuration option for > `header` throws a `BadBooleanException`. Schemagen is checking for `isTrue` > for this option while the value specified is intended to be a String. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
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" 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 early to give us discussion time. > > == Retirements > > We have talked about this before but not actually done anything. See > separate thread for discussion on retirement process and for the first > modules: > > jena-spatial > jena-fuseki1 > jena-csv > > == Headlines > > JENA-664 : GeoSPARQL support > > 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. > > JENA-1621 : Lucene upgrade to 7.4 > May need to reload lucene indexes. > (e.g. the lucene index was create originally with Lucene v5.x (prior > Jena 3.3.0). See Lucene upgrade tool. > https://lucene.apache.org/solr/guide/7_4/indexupgrader-tool.html > > JENA-1623 : Fuseki security > JENA-1627 : HTTP support > https://issues.apache.org/jira/browse/JENA-1623 > http://jena.staging.apache.org/documentation/fuseki2/data-access-control > > == JIRA: > > 31 currently. > > https://s.apache.org/jena-3.10.0-jira > > == Updates > > Only plugins. JENA-1624 > > surefire : 2.21.0 -> 2.22.1 (+ SUREFIRE-1588) > compiler : 3.7.0 -> 3.8.0 > shade: 3.1.0 -> 3.2.0 > > Andy > -- --- Marco Neumann KONA
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 early to give us discussion time. == Retirements We have talked about this before but not actually done anything. See separate thread for discussion on retirement process and for the first modules: jena-spatial jena-fuseki1 jena-csv == Headlines JENA-664 : GeoSPARQL support 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. JENA-1621 : Lucene upgrade to 7.4 May need to reload lucene indexes. (e.g. the lucene index was create originally with Lucene v5.x (prior Jena 3.3.0). See Lucene upgrade tool. https://lucene.apache.org/solr/guide/7_4/indexupgrader-tool.html JENA-1623 : Fuseki security JENA-1627 : HTTP support https://issues.apache.org/jira/browse/JENA-1623 http://jena.staging.apache.org/documentation/fuseki2/data-access-control == JIRA: 31 currently. https://s.apache.org/jena-3.10.0-jira == Updates Only plugins. JENA-1624 surefire : 2.21.0 -> 2.22.1 (+ SUREFIRE-1588) compiler : 3.7.0 -> 3.8.0 shade: 3.1.0 -> 3.2.0 Andy
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 want also to make a point of pointing at replacements, even if they seem obvious to us. ajs6f > On Nov 29, 2018, at 11:45 AM, Andy Seaborne wrote: > > 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 area "archived/" with the modules moved there. > This leaves them in the source-release and browsable in git. > > 2/ Delete from git. Maybe leave a file somewhere to record the commit ids. > > 3/ A new separate git-repo for "jena-misc" > https://git-wip-us.apache.org/repos/asf/jena-misc.asf > (or use gitbox and put it on github mirroed back to ASF.) > > and maybe some others. > > I think (1) is not definite enough. > > Thoughts/suggestions/... > >Andy > > [+] > jena-spatial :: this is in jena-fuseki-webapp > [INFO] +- org.apache.jena:jena-spatial:jar:3.10.0-SNAPSHOT:compile > [INFO] | +- org.apache.lucene:lucene-spatial:jar:7.4.0:compile > [INFO] | +- org.apache.lucene:lucene-spatial-extras:jar:7.4.0:compile > [INFO] | | +- org.apache.lucene:lucene-spatial3d:jar:7.4.0:compile > [INFO] | | \- io.sgr:s2-geometry-library-java:jar:1.0.0:compile > [INFO] | \- org.locationtech.spatial4j:spatial4j:jar:0.6:compile
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 area "archived/" with the modules moved there. This leaves them in the source-release and browsable in git. 2/ Delete from git. Maybe leave a file somewhere to record the commit ids. 3/ A new separate git-repo for "jena-misc" https://git-wip-us.apache.org/repos/asf/jena-misc.asf (or use gitbox and put it on github mirroed back to ASF.) and maybe some others. I think (1) is not definite enough. Thoughts/suggestions/... Andy [+] jena-spatial :: this is in jena-fuseki-webapp [INFO] +- org.apache.jena:jena-spatial:jar:3.10.0-SNAPSHOT:compile [INFO] | +- org.apache.lucene:lucene-spatial:jar:7.4.0:compile [INFO] | +- org.apache.lucene:lucene-spatial-extras:jar:7.4.0:compile [INFO] | | +- org.apache.lucene:lucene-spatial3d:jar:7.4.0:compile [INFO] | | \- io.sgr:s2-geometry-library-java:jar:1.0.0:compile [INFO] | \- org.locationtech.spatial4j:spatial4j:jar:0.6:compile
[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=16703427#comment-16703427 ] Andy Seaborne commented on JENA-664: [jena@dev email message|https://lists.apache.org/thread.html/a6c3375b682ca1e5af9463126385f3c0d6f2b0d9ad66a164ab4a927e@%3Cdev.jena.apache.org%3E] October 2018: [https://github.com/galbiston/geosparql-jena] > GeoSPARQL support for Jena > -- > > Key: JENA-664 > URL: https://issues.apache.org/jira/browse/JENA-664 > Project: Apache Jena > Issue Type: New Feature >Reporter: Andreas Kuckartz >Priority: Major > Labels: features, gsoc2015, gsoc2017 > > I am aware that GeoSPARQL support is available in Parliament > (http://parliament.semwebcentral.org/) but that is using the somewhat > obsolete Joseki and not Fuseki. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
