Re: [VOTE] Apache Jena 4.8.0 RC2

+1 (binding) The checksums and signatures are all good I was able to build from the git tag and the source distribution LICENSE and NOTICE files look good I have tested the release successfully in downstream projects Thank you, Andy! On Thu, Apr 20, 2023 at 9:57 PM Bruno Kinoshita wrote: >

Re: [VOTE] Apache Jena 4.7.0 RC1

[X] +1 (binding) Checked signatures and checksums Built from the source distribution Built from the git tag license/notice files look good Aaron On Tue, Dec 20, 2022 at 11:39 AM Andy Seaborne wrote: > Hi, > > Here is a vote on the release of Apache Jena 4.7.0. > This is the first release

Re: [VOTE] Apache Jena 4.6.0 RC1

[x] +1 Approve the release (binding) Built from source distribution and from git tag Signatures are all good Checksums are all good LICENSE files are present and look good NOTICE files are present and look good Thank you, Andy, once again for all that you're doing. -Aaron On Wed, Aug 24, 2022

Re: [VOTE] Apache Jena 4.5.0 RC1

[x] +1 Approve the release (binding) Verified signatures Verified checksums Built jena from source archive using Java 11 and Maven 3.8.1 All artifacts contain LICENSE and NOTICE files Thanks, Aaron On Mon, May 2, 2022 at 1:53 AM Bruno Kinoshita wrote: > [x] +1 Approve the

Re: Towards Jena 4.5.0

On Thu, Apr 28, 2022, 5:51 AM Andy Seaborne wrote: > There are several PRs in progress, in draft or in discussion, including > a new one for a replacement of the in-memory graph which is more space > efficient. > > There are also significant things ready for release; better JSON SPARQL >

Re: [VOTE] Apache Jena 4.3.2 RC 1

+1 (binding) checksums are good signatures are good LICENSE/NOTICE files are present and look good Source distribution is buildable (MacOS, jdk11) git tag is buildable (MacOS, jdk11) Aaron On Fri, 17 Dec 2021 at 15:17, Andy Seaborne wrote: > +1 (binding) > > Andy > > On 17/12/2021

Re: [VOTE] Apache Jena 4.3.1 RC 1

[X] +1 Approve the release (binding) Verified signatures Verified checksums Built from source dist with JDK 11 & 17 on Mac Built from SCM tag with JDK 11 & 17 on linux LICENSE/NOTICE files are present and look good Thanks for the quick turn-around on this. Aaron On Fri, 10 Dec 2021 at 11:40,

Re: [VOTE] Apache 4.3.0 RC 1

[X] +1 Approve the release Verified signatures Verified checksums Built on Java 11 and 17 from git tag (OS X, maven 3.8.2) Built on Java 11 and 17 from source archive (OS X, maven 3.8.2) LICENSE and NOTICE files are present Thanks for managing this release! -Aaron On Mon, 6 Dec 2021 at 03:43,

Re: Towards Jena 4.3.0

+1 On Wed, Nov 17, 2021, 20:24 wrote: > +1 indeed. > > Adam > > On Wed, Nov 17, 2021, 4:33 PM Bruno P. Kinoshita > wrote: > > > >Does that fit with PMC members? > > +1 > > Thanks Andy! > > Bruno > > > > On Wednesday, 17 November 2021, 11:09:35 pm NZDT, Andy Seaborne < > > a...@apache.org>

Re: [DRAFT] Apache Jena report - 2021-10

s in this project. > The Committer-to-PMC ratio is 9:7. > > Community changes, past quarter: > - No new PMC members. Last addition was Aaron Coburn on 2019-01-22. > - No new committers. Last addition was Greg Albiston on 2019-07-08. > > ## Project Activity: > Jena version

Re: Jena & OSGi artifacts

That particular SO issue comes from the use of Jena in the Islandora project. I reached out to some developers I know in that community to ask about their plans for using Jena in an OSGi context. Apparently, they are moving away from OSGi, likely in the direction of runnable jars. In fact, the

Re: [] Apache Jena 4.2.0 RC1

endent project. > > This delays doing another build prior to 4.3.0 until we know whether it > is needed - whether OSGi (and know it's been confirmed as working) or > some other thing that emerges. > > Andy > > On 14/09/2021 14:38, Aaron Coburn wrote: > > Hi Andy, &g

Re: [] Apache Jena 4.2.0 RC1

ntimes. All of which is to say: perhaps the Jena project should consider whether OSGi should be supported in the future. -Aaron On Tue, 14 Sept 2021 at 05:47, Andy Seaborne wrote: > > > On 14/09/2021 01:18, Aaron Coburn wrote: > ... > > I did find that the OSGi deployment faile

Re: [VOTE] Apache Jena 4.2.0 RC1

The signatures and checksums are all good. I tested Jena 4.2.0 with some downstream dependencies that I work on and everything checked out quite well, even those projects that require an older version of Titanium and those that run in a JakartaEE 8 context. I did find that the OSGi deployment

[jira] [Commented] (JENA-1948) Consider using Titanium library for JSON-LD 1.1 support

[ https://issues.apache.org/jira/browse/JENA-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395514#comment-17395514 ] Aaron Coburn commented on JENA-1948: For me, the principal use case involves reading and signing

[jira] [Commented] (JENA-1948) Consider using Titanium library for JSON-LD 1.1 support

[ https://issues.apache.org/jira/browse/JENA-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386941#comment-17386941 ] Aaron Coburn commented on JENA-1948: Starting with a reader makes a lot of sense. I have some code

[jira] [Commented] (JENA-2121) Can't use jena-core, jena-iri in modular runtime-image

[ https://issues.apache.org/jira/browse/JENA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366694#comment-17366694 ] Aaron Coburn commented on JENA-2121: Jena releases jars with Automatic-Module-Name metadata, which

Javadocs?

It seems the Javadocs for Jena have all gone missing: https://jena.apache.org/documentation/javadoc/arq/ Are they just in a different location now? (If so, we should change the links from the home page) Thanks, Aaron

Re: [VOTE] Apache Jena 4.1.0 RC 1

+1 (binding) Verified signatures and checksums Verified that the source and git tag can be built (MacOS, Java 11.0.10) Verified that the OSGi feature can be provisioned (Karaf 4.3.x) Thanks for assembling this release, Aaron On Tue, 1 Jun 2021 at 06:51, Rob Vesse wrote: > +1 (binding) > >

[jira] [Commented] (JENA-2112) ShEx engine

[ https://issues.apache.org/jira/browse/JENA-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354117#comment-17354117 ] Aaron Coburn commented on JENA-2112: ShEx comes from a W3C community group report: [https://shex.io

Re: [DRAFT] Apache Jena report (April 2021)

es requiring board attention. > > ## Membership Data: > Apache Jena was founded 2012-04-18 (9 years ago) > There are currently 18 committers and 14 PMC members in this project. > The Committer-to-PMC ratio is 9:7. > > Community changes, past quarter: > - No new PMC members. La

Re: [] Apache Jena 4.0.0 RC 1

> The deadline is Tuesday, 30 March 2021 at 21:00 UTC > > Please vote to approve this release: > > [X] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > Built fine from the git tag with Java 11.0.10, Maven 3.6.3 on OS X Also built fine

Re: [LAZY] rename default branches as 'main'.

+1 On Fri, Feb 5, 2021, 06:03 Andy Seaborne wrote: > +1 > > On 05/02/2021 10:04, Andy Seaborne wrote: > > This is a decision by lazy consensus[*]. > > > > Let's rename the default branch as 'main' for both the code repo and the > > site repo. > > > > The process is: > > > > 1/ We create a repo

Re: Java 8 or 11?

On Fri, 8 Jan 2021 at 14:33, Martynas Jusevičius wrote: > Suggestion: migrate builds to GitHub actions. I just did that for our > test suites. > > https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works +1 (I used travis-ci for a long time, but now

Re: Java 8 or 11?

At this point, Java8 is no longer supported by Oracle. (OpenJDK and AWS Corretto will both continue to support security updates), and from what I've been seeing, much of the Java ecosystem is moving in this direction, too. Everything I work on uses Java 11, so I am generally +1 on moving in this

Re: dependabot results

> BTW was there a particular fix in HttpClient 4.5.13 that you wanted? > There is a CVE for HttpClient before 4.5.13 related to a malformed authority component

Re: dependabot results and

Thanks, that was a bit of work from a question about just one dependency, but hopefully this will make maintenance quite a lot easier going forward. Aaron On Thu, Nov 12, 2020, 12:54 Andy Seaborne wrote: > OK - I think it is tamed for now! > > A lot of updates, nothing serious showing up. The

Re: Towards 3.17.0

This looks excellent. Should we also update the version of o.a.httpcomponents:httpclient? 4.5.10 => 4.5.13 Aaron On Tue, 10 Nov 2020 at 15:21, Bruno P. Kinoshita wrote: > Looks good to me. I thought there would be 5-10 issues, was surprised to > see 38! Great work, +1 > Bruno > > On

[jira] [Commented] (JENA-1948) Consider using TItanium library for JSON-LD 1.1 support

[ https://issues.apache.org/jira/browse/JENA-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183648#comment-17183648 ] Aaron Coburn commented on JENA-1948: It would definitely be worth looking at Titanium. One important

Re: [VOTE] Apache Jena 3.16.0 RC 1

[X] +1 Approve the release Built from git tag on OS X with Java version 1.8.0_231 Deploys into Karaf 4.2.8 (OSGi) Works with Java Platform Module System (Java 11) Hashes and Signatures are all good LICENSE and NOTICE files are present Thanks for preparing this release. Cheers, Aaron

Re: [VOTE] Apache Jena 3.15.0 RC 1

+1 (binding) Hashes are good Signatures are good Built successfully from release tag on SCM (using JDK 8) Built successfully from source artifact (using JDK 11) Deployed successfully into Karaf 4.2.8 Verified that Jena 3.15 works in JPMS mode under Java 11 Successfully tested the new commons-rdf

[jira] [Resolved] (JENA-1888) Mark log4j2 optional in OSGi bundle

[ https://issues.apache.org/jira/browse/JENA-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Coburn resolved JENA-1888. Resolution: Fixed > Mark log4j2 optional in OSGi bun

[jira] [Updated] (JENA-1888) Mark log4j2 optional in OSGi bundle

[ https://issues.apache.org/jira/browse/JENA-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Coburn updated JENA-1888: --- Summary: Mark log4j2 optional in OSGi bundle (was: Exclude log4j2 from OSGi bundle) > Mark log

[jira] [Updated] (JENA-1888) Mark log4j2 optional in OSGi bundle

[ https://issues.apache.org/jira/browse/JENA-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Coburn updated JENA-1888: --- Description: The jena osgi bundle has a dependency on log4j2, but this should be marked as optional

[jira] [Created] (JENA-1888) Exclude log4j2 from OSGi bundle

Aaron Coburn created JENA-1888: -- Summary: Exclude log4j2 from OSGi bundle Key: JENA-1888 URL: https://issues.apache.org/jira/browse/JENA-1888 Project: Apache Jena Issue Type: Improvement

Re: Towards Java 3.15.0

I did some initial testing of the current master branch, and generally it looks great. It builds fine with JDK 8 and 11; all tests pass. I tried using those artifacts in some downstream code, and all looks good (including with Java 11 JPMS). The only possible issue I encountered was with the OSGi

[jira] [Resolved] (JENA-1833) Add jena-commonsrdf to jena-osgi

[ https://issues.apache.org/jira/browse/JENA-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Coburn resolved JENA-1833. Assignee: Aaron Coburn Resolution: Fixed > Add jena-commonsrdf to jena-o

[jira] [Commented] (JENA-1830) travis.yml

[ https://issues.apache.org/jira/browse/JENA-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023869#comment-17023869 ] Aaron Coburn commented on JENA-1830: +1 for testing only LTS versions. If the test failures

Re: [VOTE] Apache Jena 3.14.0 RC 2

+1 (binding) Checked signatures Github tag matches Built from github tag and source release with both JDK 8 and 11 Checked JDK 11 (module) compatibility Checked OSGi artifacts The fix for JENA-1817 addressed the issue I reported earlier Aaron On Thu, 16 Jan 2020 at 12:52, Andy Seaborne wrote:

Re: [] Apache Jena 3.14.0 RC 1

something else. > > If you are able to putting in a JVM-suspend breakpoint at > ThreadBufferingCache:88 and capture a thread dump, that would be very > helpful - I realise it's not always easy to get up. > > Andy > > > > On 15/01/2020 16:55, Aaron Coburn wrote:

Re: [VOTE] Apache Jena 3.14.0 RC 1

This might be good to split off into a separate issue (and it doesn't necessarily need to block the release), but I'm finding that, when using TDB2 with this release candidate in a concurrent write context, I start encountering a lot of errors. And those errors are definitely not present with

Re: [VOTE] Split off GH PR email traffic to a new list.

+1 Thanks, Aaron On Tue, 7 Jan 2020 at 08:42, wrote: > +1. This would be great! > > Adam > > On Tue, Jan 7, 2020, 8:36 AM Andy Seaborne wrote: > > > Happy 2020 everyone. > > > > From the [DISCUSS] around: > > > > > > >

Re: Towards Jena 3.14.0

I will have time to review any release candidates between now and Jan 20. Cheers, Aaron On Tue, 7 Jan 2020 at 08:37, Andy Seaborne wrote: > It's coming up to time to look at Jena 3.14.0. v3.13.1 was 2019-10-11. > > I have time between now and January 19th to do a release or to work with >

Re: Jena next

I would be very interested in discussing the high level Java API and how it could be simplified. It might also be worthwhile to look into the overall package/jar structure. This will help for both OSGi and JPMS support. Regarding the Java14/JPMS target, I assume this means that the Jena code can

Re: [VOTE] Apache Jena 3.13.1 RC 1.

[x] +1 Approve the release (binding) The signatures and checksums are all good LICENSE and NOTICE files are present I was able to do a full build (mvn verify install) from the source artifact with Java 1.8.0_221 The Java11 automatic module names are all correct and I was able to successfully test

Re: Towards Jena 3.13.1

Next week works for me. Thanks, Aaron On Thu, Oct 3, 2019, 04:42 A. Soroka wrote: > I should be able to test on Linux and vote. > > (MacBook Pro battery bug got me, arg!) > > Adam > > On Thu, Oct 3, 2019, 9:38 AM Rob Vesse wrote: > > > I'm on a work trip next week and won't have any free time

Re: [] Apache Jena 3.13.0 RC 2

nd? > > By x.x.1, I mean specific changes only (fixes and safe/contained > changes), and certainly no new modules. > > I'd also like to find a way for more automated tests to catch things > early (won't we all?!). > > Andy > > On 9/25/19 9:00 PM, Aaron Coburn wrote: &g

[jira] [Created] (JENA-1764) Fix missing and duplicate Automatic-Module-Name metadata

Aaron Coburn created JENA-1764: -- Summary: Fix missing and duplicate Automatic-Module-Name metadata Key: JENA-1764 URL: https://issues.apache.org/jira/browse/JENA-1764 Project: Apache Jena Issue

Re: [VOTE] Apache Jena 3.13.0 RC 2

Checksums and signatures all look good. The full source release builds (and tests) for me under both JDK8 and JDK11 OSGi provisioning works One issue I found -- and this isn't necessarily a blocker because it appears that it existed before: the jena-dboe-storage artifact has an empty

Re: [CANCELLED] [VOTE] Apache Jena 3.13.0 RC 1

I can also confirm this: the build succeeds from the git tag but not from the source artifact (due to the missing file in the SHACL module) Aaron On Tue, 24 Sep 2019 at 15:13, Andy Seaborne wrote: > Due to missing files in the source-release. > > Andy > > On 24/09/2019 13:51, Andy

[jira] [Resolved] (JENA-1741) Invalid Automatic-Module-Name values

[ https://issues.apache.org/jira/browse/JENA-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Coburn resolved JENA-1741. Resolution: Fixed > Invalid Automatic-Module-Name val

[jira] [Resolved] (JENA-1742) Fix OSGi imports

[ https://issues.apache.org/jira/browse/JENA-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Coburn resolved JENA-1742. Assignee: Aaron Coburn Resolution: Fixed > Fix OSGi impo

[jira] [Created] (JENA-1742) Fix OSGi imports

Aaron Coburn created JENA-1742: -- Summary: Fix OSGi imports Key: JENA-1742 URL: https://issues.apache.org/jira/browse/JENA-1742 Project: Apache Jena Issue Type: Improvement Components

[jira] [Created] (JENA-1741) Invalid Automatic-Module-Name values

Aaron Coburn created JENA-1741: -- Summary: Invalid Automatic-Module-Name values Key: JENA-1741 URL: https://issues.apache.org/jira/browse/JENA-1741 Project: Apache Jena Issue Type: Improvement

Re: SHACL

> > > On 08/07/2019 16:28, Aaron Coburn wrote: > >> Thanks, Andy, I will likely have some data+shape resources in the coming > >> weeks/months that I would like to test. Are there plans to add this > >> code to > >> Jena itself, or do you

Re: [jena] 01/04: Build for wider range of JDKs on Travis

JDK 9 and 10 are EOL (there is really no need to test those). Java11 is a LTS edition, so it should definitely be tested. Java12 is the current non-LTS version under release, and Java13 will supersede Java12 in September. On Mon, 8 Jul 2019 at 15:30, Andy Seaborne wrote: > Rob, > > Aren't java9

Re: SHACL

Thank, Andy, I will likely have some data+shape resources in the coming weeks/months that I would like to test. Are there plans to add this code to Jena itself, or do you anticipate that it will be part of a separate repository? Best, Aaron On Mon, 8 Jul 2019 at 10:58, Andy Seaborne wrote: >

Re: [VOTE] Apache Jena 3.11.0 RC2

[x] +1 Approve this release Tested building on OS X using Java 11 and Java 8 using this command: `$ mvn clean install -Pdev` Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T14:33:14-04:00) Maven home: /usr/local/Cellar/maven/3.5.4/libexec Java version: 11.0.2, vendor:

Re: The state of jena+Java11

I think this can be fixed by setting the javadoc configuration to use Java 8 as the source. I submitted a PR to this effect here: https://github.com/apache/jena/pull/565 but please give that branch a real test on your local system before merging, I'm traveling at the moment and am not in a great

[jira] [Commented] (JENA-1704) Enable Apache Sonar reports

[ https://issues.apache.org/jira/browse/JENA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825205#comment-16825205 ] Aaron Coburn commented on JENA-1704: What I've done with some of my own projects is to add the sonar

Re: [VOTE] Apache Jena 3.11.0 RC1

Hi All, When building the source from the EDT (GMT -4) timezone, I get test failures in the o.a.j.sparql.expr.TestFunctions:localDateTime_2 test. Basically, the test is expecting the timezone value to be > -1, which would be fine for about half of the world, but that value could range anywhere

Re: Towards Jena 3.11.0

Also +1 to releasing 3.11 soon and addressing these other issues in 3.12. (But either way is fine with me) Aaron On Wed, Apr 17, 2019 at 6:47 AM wrote: > +1 to releasing 3.11.0 as described and not loading it up any further. > > ajs6f > > On Wed, Apr 17, 2019, 6:14 AM Andy Seaborne wrote: > >

Re: Sonar?

It is possible to exclude specific modules from Sonar's analysis (I do this with some of my own projects). The documentation for this is here:

Re: [VOTE] Apache Jena 3.10.0 RC1

+1 (non-binding) Builds on OS X with both Java 8 and Java 11 using Maven 3.5.4. I verified that the OSGi module works in Karaf 4.2 The Automatic-Module-Name metadata looks good across all the artifacts The Jena-based Commons-RDF module works with this RC Aaron > On Dec 31, 2018, at 11:10 AM,

[jira] [Created] (JENA-1653) Duplicate Automatic-Module-Name values

Aaron Coburn created JENA-1653: -- Summary: Duplicate Automatic-Module-Name values Key: JENA-1653 URL: https://issues.apache.org/jira/browse/JENA-1653 Project: Apache Jena Issue Type: Bug

[jira] [Assigned] (JENA-1635) Invalid Automatic-Module-Names in fuseki2 modules

[ https://issues.apache.org/jira/browse/JENA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Coburn reassigned JENA-1635: -- Assignee: Aaron Coburn > Invalid Automatic-Module-Names in fuseki2 modu

[jira] [Created] (JENA-1635) Invalid Automatic-Module-Names in fuseki2 modules

Aaron Coburn created JENA-1635: -- Summary: Invalid Automatic-Module-Names in fuseki2 modules Key: JENA-1635 URL: https://issues.apache.org/jira/browse/JENA-1635 Project: Apache Jena Issue Type

[jira] [Resolved] (JENA-1599) Upgrade to jsonld-java version 0.12.1

[ https://issues.apache.org/jira/browse/JENA-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Coburn resolved JENA-1599. Resolution: Fixed > Upgrade to jsonld-java version 0.1

[jira] [Created] (JENA-1599) Upgrade to jsonld-java version 0.12.1

Aaron Coburn created JENA-1599: -- Summary: Upgrade to jsonld-java version 0.12.1 Key: JENA-1599 URL: https://issues.apache.org/jira/browse/JENA-1599 Project: Apache Jena Issue Type: Improvement

Re: Commit workflow

Thanks Andy, this is very helpful. Best, Aaron > On Jun 20, 2018, at 6:02 AM, Andy Seaborne wrote: > > Aaron, Chris, all, > > One thing to mention - with the master repo on Apache hardware and PRs on the > mirror (which we don't have write access to) there is a workflow for merging > into

Re: Welcome Aaron!

Thanks so much, Andy! I look forward to continuing to be involved in the Jena code and community. -Aaron > On Jun 18, 2018, at 10:50 AM, Andy Seaborne wrote: > > We're pleased to announce that Aaron Coburn (acoburn@) has become > a committer for Apache Jena. >

[jira] [Created] (JENA-1557) Update OSGi imports for 3.8 release

Aaron Coburn created JENA-1557: -- Summary: Update OSGi imports for 3.8 release Key: JENA-1557 URL: https://issues.apache.org/jira/browse/JENA-1557 Project: Apache Jena Issue Type: Improvement

[jira] [Created] (JENA-1538) Include TDB2 in jena-osgi module

Aaron Coburn created JENA-1538: -- Summary: Include TDB2 in jena-osgi module Key: JENA-1538 URL: https://issues.apache.org/jira/browse/JENA-1538 Project: Apache Jena Issue Type: Improvement

[jira] [Commented] (JENA-1508) Update OSGi provisioning features

[ https://issues.apache.org/jira/browse/JENA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402394#comment-16402394 ] Aaron Coburn commented on JENA-1508: One item to note about this is that, in the Karaf 4.2.0.M2 release

[jira] [Created] (JENA-1508) Update OSGi provisioning features

Aaron Coburn created JENA-1508: -- Summary: Update OSGi provisioning features Key: JENA-1508 URL: https://issues.apache.org/jira/browse/JENA-1508 Project: Apache Jena Issue Type: Improvement

Re: Release Jena 3.5.0?

Would it make sense to add an Automatic-Module-Name header to the manifest files so that Jena is easier to use in a JDK9 context? I could even volunteer to do this. Aaron > On Oct 17, 2017, at 9:56 AM, aj...@apache.org wrote: > > Claude-- > > I see some updates available for the contract

[jira] [Commented] (JENA-1378) RDFDataMgr does not perform conneg when reading remote RDF resources

[ https://issues.apache.org/jira/browse/JENA-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103203#comment-16103203 ] Aaron Coburn commented on JENA-1378: [~andy.seaborne] thanks! The RDFParser class is new to me, and I

[jira] [Created] (JENA-1378) RDFDataMgr does not perform conneg when reading remote RDF resources

Aaron Coburn created JENA-1378: -- Summary: RDFDataMgr does not perform conneg when reading remote RDF resources Key: JENA-1378 URL: https://issues.apache.org/jira/browse/JENA-1378 Project: Apache Jena

CMS diff: Reification HowTo

Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fnotes%2Freification.mdtext Aaron Coburn Index: trunk/content/documentation/notes/reification.mdtext

Re: [VOTE] Release vote : Apache Jena 3.2.0

+1 (non-binding) Works on OS X > On Feb 2, 2017, at 7:02 AM, Andy Seaborne wrote: > > +1 (binding) > >>> Please vote to approve this release: >>> >>>[ ] +1 Approve the release >>>[ ] 0 Don't care >>>[ ] -1 Don't release, because ... >>> >>> This vote will be

[jira] [Created] (JENA-1263) Configure HTTP client to follow 303 redirects

Aaron Coburn created JENA-1263: -- Summary: Configure HTTP client to follow 303 redirects Key: JENA-1263 URL: https://issues.apache.org/jira/browse/JENA-1263 Project: Apache Jena Issue Type