GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/8
pom tweaks so it builds
.. also a spelling mistake tixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena pom-fixes
Alternatively you can
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/9
No need for license of derby.log
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena derby-log
Alternatively you can review and apply
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/10
Jena OSGi bundle
Embedding core Jena modules in a single OSGi bundle.
This works around classloader issues such as Jena's use of
`Class.forName()`, but does not yet support other OSGi bundles
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/21
Remove outdated jsonld comments
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena jena-osgi-tidy
Alternatively you can review and apply
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/25
JENA-879: Jena osgi pax exam
Fixes JENA-879 for jena-osgi-test
Replaces eosgi-maven-plugin tests with PAX Exam testing.
Tests jena-osgi with OSGi frameworks Eclipse Equinox and Apache Felix
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/26
Explanation about scope
As an explanation of scope in jena-osgi/pom.xml was requested, I added it
there.
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/27
JENA-789: Fixes FUSEKI_USER breaking logging
Q: Are there other of the FUSEKI_* variables that needs to be passed
through?
Fixes [JENA-789](https://issues.apache.org/jira/browse/JENA-789)
You
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/24
Apache jena osgi
Builds on #21 by splitting out jena-osgi* to submodules under
`apache-jena-osgi`.
Merges in #21, #22, #23
You can merge this pull request into a Git repository by running
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/22
NOTICE file for jena-osgi
stripped version of apache-jena/NOTICE
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena jena-osgi-NOTICE
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/23
rat: exlude anything under target/*
.. as it only excluded `target/.plxarc`
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena parent-rat
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/30
JENA-878: Explicit imports of org.apache.xerces.impl.dv
.. by doing Organize Imports in Eclipse.
not that it solves JENA-878, but at least we would know
more explicitly which
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/31
JENA-878 Avoid exposing xerces.impl.dv
Not quite a fix to
[JENA-878](https://issues.apache.org/jira/browse/JENA-878) - but avoid the
dangerous OSGi implications of requiring an export
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/19
Javadoc rdf lang links
Some of the javadocs linked to the wrong specifications of RDF languages.
Updated to a common style.
RDFLanguages javadoc was mostly correct.
You can merge this pull
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/20
Fuseki2: Add JSON-LD, N-Triples to Content Type dropdown
.. and XML renamed to RDF/XML
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/18
Create iri from uri
Adds `IRIfactoryI.create(java.lang.URI)` to complement JENA-846
`IRI.toURI()`.
I believe I don't need the special case `if (! uri.isAbsolute())` - see
second commit
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/28
Quieter jena-osgi-test logging
.. by setting system property
now the only noise is because of duplicate slf4j binding, as slf4j-log4j is
inherited from Jena parent.
Also fixes the missing
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/29
Jena osgi integration test
Only compile+run jena-osgi-test in `mvn install` - ignore in `mvn test`.
Note that with #28 this will also work with `mvn verify`.
You can merge this pull request
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/45
Guava as shaded dependency
(Pull request mainly for discussion)
Add Guava as a shaded dependency in a new module `jena-shadowed-ext`
that can then be used by `jena-core` for
[JENA-901
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/46
JENA-904 Avoid activeInterpreters leak
Fixes [JENA-904](https://issues.apache.org/jira/browse/JENA-904) by closing
the interpreter of the generator of /ConsumerChoicePointFrame - and making sure
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/48
JENA-901 Use Guava for cache, shadowed in jena-core
In comparison with #47, this shadows Guava directly in `jena-core` without
introducing `jena-shadowed-ext`.
This is thus acceptable
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/47
JENA-901 LPDRuleEngine cache Guava from jena-shadowed-ext
This patch builds on the discussion pull request #45 - so if #45 goes
through, this is how to use Guava within Jena - importing
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/44
JENA-901 Upper bound on LPDRuleEngine cache
Fixes JENA-901.
A better solution might be to use guava caches - but I didn't want to add
another dependency, so this fix can go into a patch release
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/41
JENA-897 Override java.io.tmpdir to write to target/
.. instead of /tmp or %TEMP%
Fixes JENA-897 (although it still needs 35 GB of disk space on Windows)
You can merge this pull request
Github user stain closed the pull request at:
https://github.com/apache/jena/pull/44
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/49
Re-enable jena-osgi-tests
Re-enable the surefire-plugin for jena-osgi-tests - as the tests didn't
actually run on the master.
It needs an explicit execution so that it runs in a later phase
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/40
JENA-871 upgrade yasr and yasqe
Upgrades yasr to 2.4.12 and yasqe to 2.3.9
Fixes JENA-871 Download Results button.
latest yasr also adds the ability to download the pivot table as a CSV
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/33
JENA-867 - temporarily disable Active? tickboxes
Disabled in UI for JENA-867 which remains open.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/35
JENA-869 Disable download button until it works again
Disabled in UI - but bug JENA-869 remains open.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/36
Jena 887 remove dead links
Dead links in index.html and header updated/disabled.
Those header links should really not be copied around on every html file!
(one of them had the wrong link
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/34
JENA-865: Include prefixes in example query
Fixes JENA-865 by explicitly requiring `owl` and `rdfs` prefixes.
Also SPARQL keywords now in consistent CAPS style.
You can merge this pull request
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/37
JENA-732 jena-maven-tools outputs to target/generated-sources/jena
fixes JENA-731 and JENA-732
This reverts the reverted commit by Benson Margulies so that generated
sources are put in `target
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/38
Jena 849 maven tools demo
Fixes JENA-849 in updated `jena-maven-tools/demo`
.. tries to not list the version numbers explicitly as they would go out of
date.
You can merge this pull request
Github user stain commented on a diff in the pull request:
https://github.com/apache/jena/pull/45#discussion_r26986995
--- Diff: jena-shadowed-ext/pom.xml ---
@@ -0,0 +1,107 @@
+?xml version=1.0 encoding=utf-8?
+!--
+ Licensed to the Apache Software Foundation (ASF
Github user stain closed the pull request at:
https://github.com/apache/jena/pull/48
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/50
JENA-909 - Docker image for Fuseki 2
JENA-909 - Docker image for Fuseki
This is based on Maven, which is run either inside the Docker image, or if
target/dist already exist in the host, use
Github user stain commented on the pull request:
https://github.com/apache/jena/pull/49#issuecomment-88636009
Strange, that error is what 820fb5e8b5b8eef319b9d2c3a4c65aa875505fb2 was
avoiding - could you try with this update? Remember to build both in same mvn
run (e.g. run from
Github user stain commented on the pull request:
https://github.com/apache/jena/pull/49#issuecomment-88637141
It is because of `mvn clean verify` not installing jena-osgi to your
`~/.m2/repository`, so jena-osgi-test would download the older SNAPSHOT (which
haven't got the `sun.misc
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/93
JENA-1039: Avoid race-condition to OWL constants
Fixes [JENA-1039](https://issues.apache.org/jira/browse/JENA-1038) race
condition.
You can merge this pull request into a Git repository by running
Github user stain commented on the issue:
https://github.com/apache/jena/pull/47
OK, I've rebased for 3.1.1-SNAPSHOT, updated for Java 8 and fixed the
System properties.
As for the `FIXME` comment let's just leave it here, unless someone
understands or would be willing
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/126
JENA-1139 workaround
This workaround for JENA-1139 concatenates
the content of the other Jena modules
`src/main/resources/META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/138
JENA-1169 Add Export Restriction READMEs
As detailed in JENA-1169 https://issues.apache.org/jira/browse/JENA-1169
this adds README notices about the Export restrictions in accordance with
http
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/140
Optional xerces bundle dependency
See also https://github.com/apache/jena/pull/134#issuecomment-209474708 of
why this should be optional.
You can merge this pull request into a Git repository
Github user stain commented on the issue:
https://github.com/apache/jena/pull/50
It looks like it - although they seem to violate the ASF release processes
as non-voted over commits are being released straight to the hub from their
master branch.
---
If your project is set up
Github user stain commented on the issue:
https://github.com/apache/jena/pull/50
I have updated https://hub.docker.com/r/stain/jena/ and
https://hub.docker.com/r/stain/jena-fuseki/ to the latest releases (3.2.0,
2.5.0).
It's now based on `java:8-jre-alpine` base image so
Github user stain closed the pull request at:
https://github.com/apache/jena/pull/50
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
Github user stain commented on the issue:
https://github.com/apache/jena/pull/139
If you get the HTTPClient working again, then you should be able to use
JSONLD-Java's
[Caching
mechanism](https://github.com/jsonld-java/jsonld-java#loading-contexts-from-classpathjar)
to avoid
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/189
JENA-1258 NodeFmtLib calls JenaSystem initializer
Fixes [JENA-1258](https://issues.apache.org/jira/browse/JENA-1258) in
`NodeFmtLib`
Note that the added `TestNodeFmtInit` test case would
Github user stain commented on the issue:
https://github.com/apache/jena/pull/189
Yes, your pull request looks like the best approach.
On 8 Nov 2016 12:33 pm, "Andy Seaborne" <notificati...@github.com> wrote:
> The better fix is to initialize in No
Github user stain commented on the issue:
https://github.com/apache/jena/pull/189
Except for `impl` packages and suffixes it is never easy for Jena users to
know what is "internal code".
If it's in
[Javadoc](https://jena.apache.org/documentation/javadoc/arq/org/a
Github user stain commented on the issue:
https://github.com/apache/jena/pull/203
For unit tests you can use a JAR-cached context by using the
[jarcache.json](https://github.com/jsonld-java/jsonld-java#loading-contexts-from-classpathjar)
approach and put it together with the JSON
Github user stain commented on the issue:
https://github.com/apache/jena/pull/413
+1 - And as the extracted code is under `org.apache.jena.ext.*` so the
modified OSGI export looks good.
---
Github user stain commented on the issue:
https://github.com/apache/jena/pull/413
Would be good for the history if this pull request (or ideally git commit)
referenced which particular commit/version of Xerces this was extracted from -
even if we are "importing from ou
Github user stain commented on a diff in the pull request:
https://github.com/apache/jena/pull/341#discussion_r161557853
--- Diff: jena-arq/testing/RIOT/URISchemes/app.nt ---
@@ -0,0 +1 @@
+
<http://www.w3.org/2000/01/rdf-schema#seeAlso>
.
--- End diff --
Github user stain commented on a diff in the pull request:
https://github.com/apache/jena/pull/341#discussion_r161557584
--- Diff: jena-arq/testing/RIOT/URISchemes/file-base.rdf ---
@@ -0,0 +1,8 @@
+http://2dee5b0a-6100-470a-a67f-1399518cb470/nested/;
--- End diff
Github user stain commented on a diff in the pull request:
https://github.com/apache/jena/pull/341#discussion_r161559455
--- Diff: jena-arq/testing/RIOT/URISchemes/app.nt ---
@@ -0,0 +1 @@
+
<http://www.w3.org/2000/01/rdf-schema#seeAlso>
.
--- End diff --
Github user stain commented on a diff in the pull request:
https://github.com/apache/jena/pull/341#discussion_r161643602
--- Diff: jena-arq/testing/RIOT/URISchemes/app.nt ---
@@ -0,0 +1 @@
+
<http://www.w3.org/2000/01/rdf-schema#seeAlso>
.
--- En
Github user stain commented on a diff in the pull request:
https://github.com/apache/jena/pull/341#discussion_r161643496
--- Diff: jena-arq/testing/RIOT/URISchemes/file-base.rdf ---
@@ -0,0 +1,8 @@
+http://2dee5b0a-6100-470a-a67f-1399518cb470/nested/;
--- End diff
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/341
JENA-1462: Tests RDF/XML parsing newer URI schemes
Tests for [JENA-1462](https://issues.apache.org/jira/browse/JENA-1462)
RIOT parsing RDF/XML with a base URI different from http/https/file
58 matches
Mail list logo
