Re: Towards Jena 3.13.0
Thanks Andy. My question been considered and I can now plan accordingly. Brian On 23/09/2019 11:46, Andy Seaborne wrote: Brian - We do not close all JIRA at every release. Jena has multiple components. We have a regular release cycle so that we do not end up with hold-ups yet make progress. https://s.apache.org/jena-3.13.0-jira lists many changes and features in this release. Personally, I think that rushing JENA-1749 may itself cause problems. The discussion is covering alternative views of what the data/query model for text is triggered by the OR feature that is useful. I hope you will be able to test any work on JENA-1749. Being open source, various options are also available: 1/ run 3.13.0 with a different version of jena-text. 2/ run 3.13.0 with a locally modified version of jena-text. 3/ run 3.12.0 with selected changes from 3.13.0. Andy On 23/09/2019 10:16, Brian McBride wrote: On 21/09/2019 13:48, Andy Seaborne wrote: The project releases every 3-4 months and we are at the 4 month end of the scale this time. OK As you can see, there are contributions in the pipeline that are waiting for release. That include per-endpoint query timeouts. Some how long would the hold-up be? Should JENA-1749 get tested before freezing in a release? I'm not advocating a significant hold up - just that the status be considered. Pre-release testing has arguably found a problem with changes in Jena text in 3.13.0-SNAPSHOT. For us they are breaking changes. Code Ferret has been looking at this but is away for 3 weeks. I think there is still 1 of those to go. The changes are to implement a new feature tagged minor. The underlying issue is quite a fundamental design issue. When Code Ferret is back on line it may get resolved quite quickly, or it may not. It could be decided to - release anyway and address later - hold off long enough to see if there is a quick fix - pull the Jena text changes from this release (if that is feasible) - wait till the jena text issues are fully resolved - ... From my own situation: I am trying to get our servers on to the latest Fuseki release. I would prefer to be able to use 3.13.0 as it has the per endpoint query timeouts I need but I can't currently because of the Jena text problem. The latest I can deploy is 3.9.0. Its not a die in the ditch thing. Arguably we are no worse off if the release goes ahead with the problem. We could wait till the next release. We may not be the only users affected. I'm willing to put some effort into this if that will help. Brian Another release will be along soon. if there's the energy, sooner than the regular tick - it depends on people having time and energy. Andy On 21/09/2019 07:21, Brian McBride wrote: Andy, Please take into consideration the status of JENA-1749. This relates to recent changes in Jena text that break existing functionality. Brian On 30/08/2019 11:34, Andy Seaborne wrote: There are some things still in progress so it looks like mid/late September. Getting ready to do the build in the next few days. Pulls waiting: PR#608 : JENA-1760: Retire jena-maven-tools PR#607 : JENA-864: Switch off checking for normal forms NFC, NFKC Status ?? JENA-1755: Improve documentation of Query Builders [WIP] Claude - do you this in 3.13.0 (and work can refine it later if wanted) or wait for now. "WIP" suggests the latter. == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN and MODE (from Marco Neumann) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build The code is still there and will included in the source-release. I think we should leave the code as-is for this release and retire it afterwards but that isn't a strong opinion. JENA-1717: Produce canonical xsd:decimal forms. JENA-1756: Dependency updates. jsonld-java :: 0.12.3 -> 0.12.5 Apache Commons Lang3 :: 3.4->3.9 Apache Commons CSV :: 1.5 -> 1.7 Apache HttpClient: 4.5.5 -> 4.5.10 Apache Commons Collections4 : 4.1 -> 4.4 Apache Commons Compress 1.18 -> 1.19 (JENA-1754 -- Brad Hards) micrometer :: 1.1.3->1.2.1 jackson-databind :: 2.9.9 -> 2.9.9.3 CVEs: JENA-1736, JENA-1738, JENA-1745 == PRs: #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. Above. == JIRA 17 and another 5 with PRs. 33 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. JENA-1760 jena-maven-tools (not released since 3.6.0) -- Brian McBride brian.mcbr...@epimorp
Re: Towards Jena 3.13.0
Brian - We do not close all JIRA at every release. Jena has multiple components. We have a regular release cycle so that we do not end up with hold-ups yet make progress. https://s.apache.org/jena-3.13.0-jira lists many changes and features in this release. Personally, I think that rushing JENA-1749 may itself cause problems. The discussion is covering alternative views of what the data/query model for text is triggered by the OR feature that is useful. I hope you will be able to test any work on JENA-1749. Being open source, various options are also available: 1/ run 3.13.0 with a different version of jena-text. 2/ run 3.13.0 with a locally modified version of jena-text. 3/ run 3.12.0 with selected changes from 3.13.0. Andy On 23/09/2019 10:16, Brian McBride wrote: On 21/09/2019 13:48, Andy Seaborne wrote: The project releases every 3-4 months and we are at the 4 month end of the scale this time. OK As you can see, there are contributions in the pipeline that are waiting for release. That include per-endpoint query timeouts. Some how long would the hold-up be? Should JENA-1749 get tested before freezing in a release? I'm not advocating a significant hold up - just that the status be considered. Pre-release testing has arguably found a problem with changes in Jena text in 3.13.0-SNAPSHOT. For us they are breaking changes. Code Ferret has been looking at this but is away for 3 weeks. I think there is still 1 of those to go. The changes are to implement a new feature tagged minor. The underlying issue is quite a fundamental design issue. When Code Ferret is back on line it may get resolved quite quickly, or it may not. It could be decided to - release anyway and address later - hold off long enough to see if there is a quick fix - pull the Jena text changes from this release (if that is feasible) - wait till the jena text issues are fully resolved - ... From my own situation: I am trying to get our servers on to the latest Fuseki release. I would prefer to be able to use 3.13.0 as it has the per endpoint query timeouts I need but I can't currently because of the Jena text problem. The latest I can deploy is 3.9.0. Its not a die in the ditch thing. Arguably we are no worse off if the release goes ahead with the problem. We could wait till the next release. We may not be the only users affected. I'm willing to put some effort into this if that will help. Brian Another release will be along soon. if there's the energy, sooner than the regular tick - it depends on people having time and energy. Andy On 21/09/2019 07:21, Brian McBride wrote: Andy, Please take into consideration the status of JENA-1749. This relates to recent changes in Jena text that break existing functionality. Brian On 30/08/2019 11:34, Andy Seaborne wrote: There are some things still in progress so it looks like mid/late September. Getting ready to do the build in the next few days. Pulls waiting: PR#608 : JENA-1760: Retire jena-maven-tools PR#607 : JENA-864: Switch off checking for normal forms NFC, NFKC Status ?? JENA-1755: Improve documentation of Query Builders [WIP] Claude - do you this in 3.13.0 (and work can refine it later if wanted) or wait for now. "WIP" suggests the latter. == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN and MODE (from Marco Neumann) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build The code is still there and will included in the source-release. I think we should leave the code as-is for this release and retire it afterwards but that isn't a strong opinion. JENA-1717: Produce canonical xsd:decimal forms. JENA-1756: Dependency updates. jsonld-java :: 0.12.3 -> 0.12.5 Apache Commons Lang3 :: 3.4->3.9 Apache Commons CSV :: 1.5 -> 1.7 Apache HttpClient: 4.5.5 -> 4.5.10 Apache Commons Collections4 : 4.1 -> 4.4 Apache Commons Compress 1.18 -> 1.19 (JENA-1754 -- Brad Hards) micrometer :: 1.1.3->1.2.1 jackson-databind :: 2.9.9 -> 2.9.9.3 CVEs: JENA-1736, JENA-1738, JENA-1745 == PRs: #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. Above. == JIRA 17 and another 5 with PRs. 33 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. JENA-1760 jena-maven-tools (not released since 3.6.0)
Re: Towards Jena 3.13.0
On 21/09/2019 13:48, Andy Seaborne wrote: The project releases every 3-4 months and we are at the 4 month end of the scale this time. OK As you can see, there are contributions in the pipeline that are waiting for release. That include per-endpoint query timeouts. Some how long would the hold-up be? Should JENA-1749 get tested before freezing in a release? I'm not advocating a significant hold up - just that the status be considered. Pre-release testing has arguably found a problem with changes in Jena text in 3.13.0-SNAPSHOT. For us they are breaking changes. Code Ferret has been looking at this but is away for 3 weeks. I think there is still 1 of those to go. The changes are to implement a new feature tagged minor. The underlying issue is quite a fundamental design issue. When Code Ferret is back on line it may get resolved quite quickly, or it may not. It could be decided to - release anyway and address later - hold off long enough to see if there is a quick fix - pull the Jena text changes from this release (if that is feasible) - wait till the jena text issues are fully resolved - ... From my own situation: I am trying to get our servers on to the latest Fuseki release. I would prefer to be able to use 3.13.0 as it has the per endpoint query timeouts I need but I can't currently because of the Jena text problem. The latest I can deploy is 3.9.0. Its not a die in the ditch thing. Arguably we are no worse off if the release goes ahead with the problem. We could wait till the next release. We may not be the only users affected. I'm willing to put some effort into this if that will help. Brian Another release will be along soon. if there's the energy, sooner than the regular tick - it depends on people having time and energy. Andy On 21/09/2019 07:21, Brian McBride wrote: Andy, Please take into consideration the status of JENA-1749. This relates to recent changes in Jena text that break existing functionality. Brian On 30/08/2019 11:34, Andy Seaborne wrote: There are some things still in progress so it looks like mid/late September. Getting ready to do the build in the next few days. Pulls waiting: PR#608 : JENA-1760: Retire jena-maven-tools PR#607 : JENA-864: Switch off checking for normal forms NFC, NFKC Status ?? JENA-1755: Improve documentation of Query Builders [WIP] Claude - do you this in 3.13.0 (and work can refine it later if wanted) or wait for now. "WIP" suggests the latter. == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN and MODE (from Marco Neumann) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build The code is still there and will included in the source-release. I think we should leave the code as-is for this release and retire it afterwards but that isn't a strong opinion. JENA-1717: Produce canonical xsd:decimal forms. JENA-1756: Dependency updates. jsonld-java :: 0.12.3 -> 0.12.5 Apache Commons Lang3 :: 3.4->3.9 Apache Commons CSV :: 1.5 -> 1.7 Apache HttpClient: 4.5.5 -> 4.5.10 Apache Commons Collections4 : 4.1 -> 4.4 Apache Commons Compress 1.18 -> 1.19 (JENA-1754 -- Brad Hards) micrometer :: 1.1.3->1.2.1 jackson-databind :: 2.9.9 -> 2.9.9.3 CVEs: JENA-1736, JENA-1738, JENA-1745 == PRs: #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. Above. == JIRA 17 and another 5 with PRs. 33 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. JENA-1760 jena-maven-tools (not released since 3.6.0) -- Brian McBride brian.mcbr...@epimorphics.com Epimorphics Ltd www.epimorphics.com Court Lodge, 105 High Street, Portishead, Bristol BS20 6PT Tel: 01275 399069 Epimorphics Ltd. is a limited company registered in England (number 7016688) Registered address: Court Lodge, 105 High Street, Portishead, Bristol BS20 6PT, UK
Re: Towards Jena 3.13.0
The project releases every 3-4 months and we are at the 4 month end of the scale this time. As you can see, there are contributions in the pipeline that are waiting for release. That include per-endpoint query timeouts. Some how long would the hold-up be? Should JENA-1749 get tested before freezing in a release? Another release will be along soon. if there's the energy, sooner than the regular tick - it depends on people having time and energy. Andy On 21/09/2019 07:21, Brian McBride wrote: Andy, Please take into consideration the status of JENA-1749. This relates to recent changes in Jena text that break existing functionality. Brian On 30/08/2019 11:34, Andy Seaborne wrote: There are some things still in progress so it looks like mid/late September. Getting ready to do the build in the next few days. Pulls waiting: PR#608 : JENA-1760: Retire jena-maven-tools PR#607 : JENA-864: Switch off checking for normal forms NFC, NFKC Status ?? JENA-1755: Improve documentation of Query Builders [WIP] Claude - do you this in 3.13.0 (and work can refine it later if wanted) or wait for now. "WIP" suggests the latter. == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN and MODE (from Marco Neumann) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build The code is still there and will included in the source-release. I think we should leave the code as-is for this release and retire it afterwards but that isn't a strong opinion. JENA-1717: Produce canonical xsd:decimal forms. JENA-1756: Dependency updates. jsonld-java :: 0.12.3 -> 0.12.5 Apache Commons Lang3 :: 3.4->3.9 Apache Commons CSV :: 1.5 -> 1.7 Apache HttpClient: 4.5.5 -> 4.5.10 Apache Commons Collections4 : 4.1 -> 4.4 Apache Commons Compress 1.18 -> 1.19 (JENA-1754 -- Brad Hards) micrometer :: 1.1.3->1.2.1 jackson-databind :: 2.9.9 -> 2.9.9.3 CVEs: JENA-1736, JENA-1738, JENA-1745 == PRs: #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. Above. == JIRA 17 and another 5 with PRs. 33 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. JENA-1760 jena-maven-tools (not released since 3.6.0)
Re: Towards Jena 3.13.0
Andy, Please take into consideration the status of JENA-1749. This relates to recent changes in Jena text that break existing functionality. Brian On 30/08/2019 11:34, Andy Seaborne wrote: There are some things still in progress so it looks like mid/late September. Getting ready to do the build in the next few days. Pulls waiting: PR#608 : JENA-1760: Retire jena-maven-tools PR#607 : JENA-864: Switch off checking for normal forms NFC, NFKC Status ?? JENA-1755: Improve documentation of Query Builders [WIP] Claude - do you this in 3.13.0 (and work can refine it later if wanted) or wait for now. "WIP" suggests the latter. == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN and MODE (from Marco Neumann) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build The code is still there and will included in the source-release. I think we should leave the code as-is for this release and retire it afterwards but that isn't a strong opinion. JENA-1717: Produce canonical xsd:decimal forms. JENA-1756: Dependency updates. jsonld-java :: 0.12.3 -> 0.12.5 Apache Commons Lang3 :: 3.4->3.9 Apache Commons CSV :: 1.5 -> 1.7 Apache HttpClient: 4.5.5 -> 4.5.10 Apache Commons Collections4 : 4.1 -> 4.4 Apache Commons Compress 1.18 -> 1.19 (JENA-1754 -- Brad Hards) micrometer :: 1.1.3->1.2.1 jackson-databind :: 2.9.9 -> 2.9.9.3 CVEs: JENA-1736, JENA-1738, JENA-1745 == PRs: #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. Above. == JIRA 17 and another 5 with PRs. 33 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. JENA-1760 jena-maven-tools (not released since 3.6.0) -- Brian McBride brian.mcbr...@epimorphics.com Epimorphics Ltd www.epimorphics.com Court Lodge, 105 High Street, Portishead, Bristol BS20 6PT Tel: 01275 399069 Epimorphics Ltd. is a limited company registered in England (number 7016688) Registered address: Court Lodge, 105 High Street, Portishead, Bristol BS20 6PT, UK
Re: Towards Jena 3.13.0
On 30/08/2019 11:34, Andy Seaborne wrote: There are some things still in progress so it looks like mid/late September. Getting ready to do the build in the next few days. Pulls waiting: PR#608 : JENA-1760: Retire jena-maven-tools PR#607 : JENA-864: Switch off checking for normal forms NFC, NFKC Status ?? JENA-1755: Improve documentation of Query Builders [WIP] Claude - do you this in 3.13.0 (and work can refine it later if wanted) or wait for now. "WIP" suggests the latter. == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN and MODE (from Marco Neumann) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build The code is still there and will included in the source-release. I think we should leave the code as-is for this release and retire it afterwards but that isn't a strong opinion. JENA-1717: Produce canonical xsd:decimal forms. JENA-1756: Dependency updates. jsonld-java :: 0.12.3 -> 0.12.5 Apache Commons Lang3 :: 3.4->3.9 Apache Commons CSV :: 1.5 -> 1.7 Apache HttpClient: 4.5.5 -> 4.5.10 Apache Commons Collections4 : 4.1 -> 4.4 Apache Commons Compress 1.18 -> 1.19 (JENA-1754 -- Brad Hards) micrometer :: 1.1.3->1.2.1 jackson-databind :: 2.9.9 -> 2.9.9.3 CVEs: JENA-1736, JENA-1738, JENA-1745 == PRs: #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. Above. == JIRA 17 and another 5 with PRs. 33 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. JENA-1760 jena-maven-tools (not released since 3.6.0)
Re: Towards Jena 3.13.0
All: 1/ There have been two significant TDB2 reports, both now fixed for 3.13.0. 2/ JENA-1757 - this is deprecating graph statistic handler and removing its tests. As far as I know, this serves no purpose any more and I suggest deprecating now, with an view to removal. In Jena itself, only graph mem implements it. Andy On 30/08/2019 22:08, Andy Seaborne wrote: Certainly. (I was just scraping the JIRA for this dev@ message) Andy On 30/08/2019 12:16, Marco Neumann wrote: thank you Andy, for documentation purposes please include the MODE function that I have contributed along with the MEDIAN function for SPARQL in the item list as well. in the future there might be an interest in the community to extend the new MODE function with a bi or multimode function. but for now its just single MODE. btw the commit contains tests as well. Best, Marco On Fri, Aug 30, 2019 at 11:34 AM Andy Seaborne wrote: It's about time to look at Jena 3.13.0. There are some things still in progress so it looks like mid/late September. Any thing missed? Andy == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN (from Marco) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build JENA-1717: Produce canonical xsd:decimal forms. == PRs: #595 : JENA-1731: Fuseki service configuration #594 : JENA-1742: Fix OSGi imports #593 : JENA-1741: Invalid Automatic-Module-Name values #586 : JENA-1733: SHACL engine, command line validator This is better after #595 because it provides a Fuseki extension. #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. cd == JIRA 17 and another 5 with PRs. 3 are jackson-databind updates for CVEs: JENA-1736, JENA-1738, JENA-1745 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. jena-maven-tools (not released since 3.6.0)
Re: Towards Jena 3.13.0
Certainly. (I was just scraping the JIRA for this dev@ message) Andy On 30/08/2019 12:16, Marco Neumann wrote: thank you Andy, for documentation purposes please include the MODE function that I have contributed along with the MEDIAN function for SPARQL in the item list as well. in the future there might be an interest in the community to extend the new MODE function with a bi or multimode function. but for now its just single MODE. btw the commit contains tests as well. Best, Marco On Fri, Aug 30, 2019 at 11:34 AM Andy Seaborne wrote: It's about time to look at Jena 3.13.0. There are some things still in progress so it looks like mid/late September. Any thing missed? Andy == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN (from Marco) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build JENA-1717: Produce canonical xsd:decimal forms. == PRs: #595 : JENA-1731: Fuseki service configuration #594 : JENA-1742: Fix OSGi imports #593 : JENA-1741: Invalid Automatic-Module-Name values #586 : JENA-1733: SHACL engine, command line validator This is better after #595 because it provides a Fuseki extension. #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. == JIRA 17 and another 5 with PRs. 3 are jackson-databind updates for CVEs: JENA-1736, JENA-1738, JENA-1745 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. jena-maven-tools (not released since 3.6.0)
Re: Towards Jena 3.13.0
thank you Andy, for documentation purposes please include the MODE function that I have contributed along with the MEDIAN function for SPARQL in the item list as well. in the future there might be an interest in the community to extend the new MODE function with a bi or multimode function. but for now its just single MODE. btw the commit contains tests as well. Best, Marco On Fri, Aug 30, 2019 at 11:34 AM Andy Seaborne wrote: > It's about time to look at Jena 3.13.0. > > There are some things still in progress so it looks like mid/late > September. > > Any thing missed? > > Andy > > == Major items > > JENA-1733: A SHACL engine > JENA-1732: Lucene OR fields > JENA-1693: Add Aggregate Function MEDIAN (from Marco) > JENA-1731: Fuseki endpoint configuration improvements and refactoring > JENA-1695: DB storage refactoring > JENA-1718: Remove jena-spatial from the build > JENA-1717: Produce canonical xsd:decimal forms. > > == PRs: > > #595 : JENA-1731: Fuseki service configuration > #594 : JENA-1742: Fix OSGi imports > #593 : JENA-1741: Invalid Automatic-Module-Name values > #586 : JENA-1733: SHACL engine, command line validator >This is better after #595 because it provides a Fuseki extension. > #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server >As in the discussion, I'd like to use the same way to deal with >symlinks in scripts but getting the improvement in for the release, >and refining as time permits is better process. > > == JIRA > > 17 and another 5 with PRs. > > 3 are jackson-databind updates for CVEs: JENA-1736, JENA-1738, JENA-1745 > > https://s.apache.org/jena-3.13.0-jira > > == Retirement > > Suggestion for retirement, that is remove the code and put a README.md > in the module root directory. > >jena-maven-tools (not released since 3.6.0) > -- --- Marco Neumann KONA
Towards Jena 3.13.0
It's about time to look at Jena 3.13.0. There are some things still in progress so it looks like mid/late September. Any thing missed? Andy == Major items JENA-1733: A SHACL engine JENA-1732: Lucene OR fields JENA-1693: Add Aggregate Function MEDIAN (from Marco) JENA-1731: Fuseki endpoint configuration improvements and refactoring JENA-1695: DB storage refactoring JENA-1718: Remove jena-spatial from the build JENA-1717: Produce canonical xsd:decimal forms. == PRs: #595 : JENA-1731: Fuseki service configuration #594 : JENA-1742: Fix OSGi imports #593 : JENA-1741: Invalid Automatic-Module-Name values #586 : JENA-1733: SHACL engine, command line validator This is better after #595 because it provides a Fuseki extension. #585 : JENA-1735 : symlinks in apache-jena-fuseki/fuseki-server As in the discussion, I'd like to use the same way to deal with symlinks in scripts but getting the improvement in for the release, and refining as time permits is better process. == JIRA 17 and another 5 with PRs. 3 are jackson-databind updates for CVEs: JENA-1736, JENA-1738, JENA-1745 https://s.apache.org/jena-3.13.0-jira == Retirement Suggestion for retirement, that is remove the code and put a README.md in the module root directory. jena-maven-tools (not released since 3.6.0)
