Re: Draft: Retiring Jena modules.
Basically LGTM, but it might be nice to mention the specific GeoSPARQL impl under consideration. ajs6f > On Dec 13, 2018, at 6:53 AM, Andy Seaborne wrote: > > Draft for users@ > -- > > Hi Jena users, > > The project team is looking at retiring some lesser used modules. > > In the next release, modules: > > jena-fuseki1 > jena-csv > > will not be part of the release and there won't be maven artifacts. There > haven't been any changes to these modules and the code will be available from > git history. > > Beyond that we are looking at the status of: > > jena-spatial - to be replaced by a GeoSPARQL implemenetation > jena-sdb > jena-maven-tools - moving command line schemagen to jena-cmds. > > We're looking for feedback so please let us know if you use these modules > from a recent version of Jena. > >Andy >on behalf of the Jena dev team.
Re: Toward Jena 3.10.0
I would certainly recommend to keep jena-spatial for now and continue testing jena-GeoSPARQL in parallel an upcoming release. Also I am not sure if you can manage to hook GeoSPARQL into 3.10 in a timely fashion for a 2018 release. Keep in mind the switch from W3C geo:lat/long to OGC WKT:Point will cause some pain to jena users. no need to take away jena-spatial at this point. On Thu, Dec 13, 2018 at 12:01 PM Andy Seaborne wrote: > > On 04/12/2018 12:56, Greg Albiston wrote: > > There is probably a broader question as to how/if these options should > > be integrated in with Fuseki, whether it should be a separate > > application or they should be left out. I think they are useful to a > > user who is looking for a GeoSPARQL solution. Currently, > > GeoSPARQL-Fuseki is using the main/embedded server so doesn't have a > > GUI etc. > > The ideal way is to have an assembler for the GeoSPARQL dataset - does > that style work here? If it also needs server-wide settings, they can be > either done on the server level object or done in the GeoSPARQL dataset > assembler with the caution of what happens if there are 2+ such datasets > and different settings. > > Given that, would it be better to not immediately jump to retiring > jena-spatial (given that we had a users@ email this week and that's a > rare occurrence!). I'm neutral and wil go with whatever people who have > better knowledge determine to be the best approach. > > Andy > > > -- --- Marco Neumann KONA
Re: [DISCUSS] Move Jena repo to gitbox or github
I have released Jena, at least once (I think maybe twice and I've forgotten!). It is _easy_. A lot is already scripted or automated in Maven. Honestly, the worst part is dealing with our SVN-based site, because it's big enough that one often has to break up large commits. It's really easy, and even fun. :grin: ajs6f > On Dec 12, 2018, at 3:26 PM, Bruno P. Kinoshita > wrote: > > I only released Apache Commons components. Would Jena be too > different/complex? > > I have GitHub 2FA, ASF gpg keys (4096), Maven settings.xml set up for ASF > maven repo. So if the process is not too hard for a beginner, I can volunteer > to either sidekick and review/learn the process, or to RM 3.10.0. > > I haven't done much Jena development, so maybe I can help running releases > and website migration & issues for now :) (also want to discuss Fuseki JS web > layer later, as backbone.js isn't being used much lately, and we could try > something simpler perhaps). > > > Cheers > Bruno > > > > From: Andy Seaborne > To: dev@jena.apache.org > Sent: Thursday, 13 December 2018 7:29 AM > Subject: Re: [DISCUSS] Move Jena repo to gitbox or github > > > > > > On 12/12/2018 15:53, Chris Tomlinson wrote: >> Hi Andy, >> >>> On Dec 12, 2018, at 7:35 AM, Andy Seaborne wrote: >>> >>> >>> >>> On 11/12/2018 17:19, Chris Tomlinson wrote: Hi Andy, My GH and ASF accounts are linked. As I understand the note from D.Gruno once jena is moved to GB then we can use either GB or GH or both in our individual workflows. For me just working with GH would be my choice. I’m not sure how far away 3.10.0 is (I’ve completed all of the pending jena-text updates for 3.10.0) but maybe it makes sense if that release can be completed prior to moving from git-wip-us without running into the forced move beginning on 7 Feb 2019. >>> >>> I'd like to avoid a forced move, if nothing else, out of politeness to >>> INFRA because they asked nicely. >> >> I certainly agree that we’d be better served by orchestrating a voluntary >> move. How far away is 3.10.0? > > Ssh! but I _hope_ end of Dec. Ish. Maybe slip into Jan. > > I'm not so worried about the git repo changes affecting things very > much. It happens automatically and at a point in time. Might/should > work to just edit .git/config > > > Andy > >> >> Regards, >> Chris >>
Re: Toward Jena 3.10.0
On 04/12/2018 12:56, Greg Albiston wrote: > There is probably a broader question as to how/if these options should > be integrated in with Fuseki, whether it should be a separate > application or they should be left out. I think they are useful to a > user who is looking for a GeoSPARQL solution. Currently, > GeoSPARQL-Fuseki is using the main/embedded server so doesn't have a > GUI etc. The ideal way is to have an assembler for the GeoSPARQL dataset - does that style work here? If it also needs server-wide settings, they can be either done on the server level object or done in the GeoSPARQL dataset assembler with the caution of what happens if there are 2+ such datasets and different settings. Given that, would it be better to not immediately jump to retiring jena-spatial (given that we had a users@ email this week and that's a rare occurrence!). I'm neutral and wil go with whatever people who have better knowledge determine to be the best approach. Andy
Draft: Retiring Jena modules.
Draft for users@ -- Hi Jena users, The project team is looking at retiring some lesser used modules. In the next release, modules: jena-fuseki1 jena-csv will not be part of the release and there won't be maven artifacts. There haven't been any changes to these modules and the code will be available from git history. Beyond that we are looking at the status of: jena-spatial - to be replaced by a GeoSPARQL implemenetation jena-sdb jena-maven-tools - moving command line schemagen to jena-cmds. We're looking for feedback so please let us know if you use these modules from a recent version of Jena. Andy on behalf of the Jena dev team.
Re: Module retirement
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 attention? This isn't a definite "will be retired"; it is a "the project is looking at the status of". I think we should throw the net quite widely - we need feedback and interest and indeed contributions for modules to be worth the effort. Draft message coming up. Detailed process: First step - remove jena-fuseki1 and jena-csv from build; see PR#508. Then delete the code before 3.10, leaving just the directory and a README saying "Gone!" and say you can pull from git history. These stubs can exist for 3.10.0 release and sometime we can delete the module stubs entirely. Sound good? Andy On 29/11/2018 17:08, ajs6f wrote: 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] [Issue Comment Deleted] (JENA-1650) Retire Apache Jena CSV module.
[ https://issues.apache.org/jira/browse/JENA-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-1650: Comment: was deleted (was: Pull request: https://github.com/apache/jena/pull/508 ) > Retire Apache Jena CSV module. > -- > > Key: JENA-1650 > URL: https://issues.apache.org/jira/browse/JENA-1650 > Project: Apache Jena > Issue Type: Task >Affects Versions: Jena 3.9.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Critical > Fix For: Jena 3.10.0 > > > Retire jena-csv. > This an action from the dev@ discussion: > https://lists.apache.org/thread.html/b89873afba86864994d0515a4c49889c6356d1c91071964eaa1014d1@%3Cdev.jena.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1650) Retire Apache Jena CSV module.
[ https://issues.apache.org/jira/browse/JENA-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720065#comment-16720065 ] Andy Seaborne commented on JENA-1650: - Pull request: https://github.com/apache/jena/pull/508 > Retire Apache Jena CSV module. > -- > > Key: JENA-1650 > URL: https://issues.apache.org/jira/browse/JENA-1650 > Project: Apache Jena > Issue Type: Task >Affects Versions: Jena 3.9.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Critical > Fix For: Jena 3.10.0 > > > Retire jena-csv. > This an action from the dev@ discussion: > https://lists.apache.org/thread.html/b89873afba86864994d0515a4c49889c6356d1c91071964eaa1014d1@%3Cdev.jena.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1649) Retire Apache Jena Fuseki1 module.
[ https://issues.apache.org/jira/browse/JENA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720056#comment-16720056 ] ASF GitHub Bot commented on JENA-1649: -- GitHub user afs opened a pull request: https://github.com/apache/jena/pull/508 JENA-1649, JENA-1650: Remove jena-csv and jena-fuseki1 from the build This removed jena-csv and jena-fuseki1 from the top POM. You can merge this pull request into a Git repository by running: $ git pull https://github.com/afs/jena retire1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/508.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #508 commit 65728fb333642eed356532aae8a385bc0ca8fea7 Author: Andy Seaborne Date: 2018-12-13T11:10:12Z JENA-1649, JENA-1650: Remove jena-csv and jena-fuseki1 from the build > Retire Apache Jena Fuseki1 module. > -- > > Key: JENA-1649 > URL: https://issues.apache.org/jira/browse/JENA-1649 > Project: Apache Jena > Issue Type: Task >Affects Versions: Jena 3.9.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Critical > Fix For: Jena 3.10.0 > > > Retire Fuseki1. > This an action from the dev@ discussion: > https://lists.apache.org/thread.html/b89873afba86864994d0515a4c49889c6356d1c91071964eaa1014d1@%3Cdev.jena.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] jena pull request #508: JENA-1649, JENA-1650: Remove jena-csv and jena-fusek...
GitHub user afs opened a pull request: https://github.com/apache/jena/pull/508 JENA-1649, JENA-1650: Remove jena-csv and jena-fuseki1 from the build This removed jena-csv and jena-fuseki1 from the top POM. You can merge this pull request into a Git repository by running: $ git pull https://github.com/afs/jena retire1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/508.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #508 commit 65728fb333642eed356532aae8a385bc0ca8fea7 Author: Andy Seaborne Date: 2018-12-13T11:10:12Z JENA-1649, JENA-1650: Remove jena-csv and jena-fuseki1 from the build ---
[jira] [Created] (JENA-1649) Retire Apache Jena Fuseki1 module.
Andy Seaborne created JENA-1649: --- Summary: Retire Apache Jena Fuseki1 module. Key: JENA-1649 URL: https://issues.apache.org/jira/browse/JENA-1649 Project: Apache Jena Issue Type: Task Affects Versions: Jena 3.9.0 Reporter: Andy Seaborne Assignee: Andy Seaborne Fix For: Jena 3.10.0 Retire Fuseki1. This an action from the dev@ discussion: https://lists.apache.org/thread.html/b89873afba86864994d0515a4c49889c6356d1c91071964eaa1014d1@%3Cdev.jena.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JENA-1650) Retire Apache Jena CSV module.
Andy Seaborne created JENA-1650: --- Summary: Retire Apache Jena CSV module. Key: JENA-1650 URL: https://issues.apache.org/jira/browse/JENA-1650 Project: Apache Jena Issue Type: Task Affects Versions: Jena 3.9.0 Reporter: Andy Seaborne Assignee: Andy Seaborne Fix For: Jena 3.10.0 Retire jena-csv. This an action from the dev@ discussion: https://lists.apache.org/thread.html/b89873afba86864994d0515a4c49889c6356d1c91071964eaa1014d1@%3Cdev.jena.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
