[GitHub] jena pull request: pom tweaks so it builds
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 review and apply these changes as the patch at: https://github.com/apache/jena/pull/8.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 #8 commit 1957808b34a408bf0278cfb4017d6e7040eebabb Author: Stian Soiland-Reyes soiland-re...@cs.manchester.ac.uk Date: 2014-10-28T16:03:15Z pom tweaks so it builds .. also a spelling mistake tixed --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: No need for license of derby.log
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 these changes as the patch at: https://github.com/apache/jena/pull/9.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 #9 commit 2df3083c108b047d4f6f059a27da127a90a70ddc Author: Stian Soiland-Reyes soiland-re...@cs.manchester.ac.uk Date: 2014-10-28T16:35:57Z No need for license of derby.log --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Jena OSGi bundle
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 to easily plug in 3rd party Jena implementations of say readers and writers. Modules included: * jena-core * jena-arq * jena-tdb * jena-sdb * jena-iri This OSGi bundle includes a dependency on the `httpclient-osgi` and `httpcore-osgi` version. All other packages used are embeded within the OSGi bundle, making them appear on a single classloader in OSGi. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena jena-osgi-bundle Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/10.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 #10 commit 1957808b34a408bf0278cfb4017d6e7040eebabb Author: Stian Soiland-Reyes soiland-re...@cs.manchester.ac.uk Date: 2014-10-28T16:03:15Z pom tweaks so it builds .. also a spelling mistake tixed commit 5724c31d542d7c8ddf89c4333fbe4809d7783f49 Author: Stian Soiland-Reyes soiland-re...@cs.manchester.ac.uk Date: 2014-10-28T16:34:59Z Embedding all Jena modules in a single OSGi bundle. commit 3bb12d0a1472977cfcd51abf392683659bac1e4d Author: Stian Soiland-Reyes soiland-re...@cs.manchester.ac.uk Date: 2014-10-28T16:38:00Z httpcore-osgi 4.2.5 commit aa705c9e3e4f3b4c58924e95aa223213358b08e3 Author: Stian Soiland-Reyes soiland-re...@cs.manchester.ac.uk Date: 2014-10-28T16:42:48Z ver.* properties as in jena-parent TODO: Move these properties to jena-parent? --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Remove outdated jsonld comments
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 these changes as the patch at: https://github.com/apache/jena/pull/21.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 #21 commit 35a3f1de5708f54ee7a776ae9bfbdf8b02be89da Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T10:41:17Z Remove outdated jsonld comments --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-879: Jena osgi pax exam
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. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena jena-osgi-pax-exam Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/25.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 #25 commit dd9e73d8eaa7bed2148cbb3e92c89be9dfb97b94 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T23:36:45Z JENA-879: remove eosgi dependency (LGPL) commit 9bc0e0db9f5d5e9a026f5a17fd46284080cfcbb1 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T23:38:34Z JENA-879: Reformat pom.xml commit 56c4d5ad815c8d7419233b53eec992926bd90d05 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T23:43:16Z JENA-879: Removed Activator commit 4b265ff3cf57d776e3bd71f7b7937d77ef30a18d Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T23:43:26Z JENA-879: PAX dependencies ..according to https://ops4j1.jira.com/wiki/display/PAXEXAM4/OSGi+Containers but with slf4j-log4j instead of logback to be license safe. (logback 0.9.18 or later should be ASF-OK though, as it's now both LGPL and EPL http://logback.qos.ch/license.html ) commit 474a30cb68be2bcf2cfe1d0ad9415c240b4c1a24 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T23:45:45Z JENA-879: No need for junit tests interface JenaOSGITest under PAX commit bd605ee56fe1037d89aeee93b59d39d88a80bd55 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T23:47:19Z JENA-879: JenaOSGITestImpl renamed to JenaOSGITest javadoc updated commit 60f192194a8196ffef2ab4f2a4556a2a70a67cb4 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T23:54:49Z JENA-879: JenaOSGITest modified to use PaxExam https://ops4j1.jira.com/wiki/display/PAXEXAM4/Getting+Started+with+OSGi+Tests commit 4823f76479ced0c5156fb42385301fb63dba107c Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T23:55:06Z JENA-879: src/main/java - src/test/java commit 1d29f2fb114ac876f3fe4658cfdade1c9e5be8ce Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T00:09:53Z Use forked configuration to avoid classpath leakage commit d5a34394d4af0afd44765fbe149f81a50e409e57 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T00:28:26Z JENA-879: Manually list transitive OSGi bundle dependencies for PAX commit 88dcffc137e5e5d761a709c0bca00355ebc723db Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T00:42:46Z JENA-879: pax-exam-container-native instead of -forked commit 0e195c479b7dd92295e0a9df9aae2b67c3bd7102 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T00:42:54Z JENA-879: avoiding .versionAsInProject which PAX didn't like commit 31497397eb09ad9655ea5b67bccc762ba2b9fcbe Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T01:22:08Z JENA-879: using linkBundle and newer dependencies commit 2b5ba82b4e1b50b84033c7af2ca94a53f7af6540 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T01:46:39Z JENA-879: PAX logging dependencies solved it! commit 3a151b940cf04a0a0824bae15d68a65bb1ba24e8 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T02:05:07Z JENA-879: scope test commit a9450472d1adb08a4d0f5be31756c0d2489f64a8 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T11:31:10Z JENA-879: Optional way to test with eclipse equinox (NOTE: testing with both at the same time kindof works, but shows confusing errors from equinox) ) commit 32f331b972305b36d9be36df0e74328412caa7c9 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T11:37:22Z JENA-879: Also test with equinox --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Explanation about scope
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.com/stain/jena osgi-pom-comments Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/26.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 #26 commit caeb5cb1780f926d1c6cb9d67c6321e08f5d3754 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-03T12:14:20Z Explanation about scope --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-789: Fixes FUSEKI_USER breaking logging
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 can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-789-fuseki-non-root Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/27.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 #27 commit 00e6b1254f2684f5e8ba3818e346e15cff5844ea Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-04T12:18:18Z JENA-789: Fixes FUSEKI_USER breaking logging Are there other of the FUSEKI_* variables that needs to be passed through? --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Apache jena osgi
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: $ git pull https://github.com/stain/jena apache-jena-osgi Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/24.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 #24 commit 35a3f1de5708f54ee7a776ae9bfbdf8b02be89da Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T10:41:17Z Remove outdated jsonld comments commit be3b4a8975a0b3c5ac99a00278ef9cf4d082ab6c Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T10:54:01Z Move jena-osgi* to apache-jena-osgi/ commit f468945991eac63ce5d1a19fda81c7386823ec4d Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T10:54:47Z 15s = 15000 ms commit d9fb7405d6a335278dce620ab63dcd3342e6551e Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T11:06:21Z rat: exclude anything in target/, not just .plxarc commit dbf38d80ee955261f0dd915b8558c2bd0a3e7e0c Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T11:45:04Z NOTICE .. but only for things included in JAR, e.g. xercesImpl and org.apache.jena.* commit d5e30c4f137e7b0953f71f923088ac4469c1760b Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T11:58:47Z jna.nosys - avoid JNA error commit 5a89500065853f198e3b29b2c9d40d9c08e3c907 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:35:29Z NOTICE file for jena-osgi stripped version of apache-jena/NOTICE commit 77e99e5e4cb6acf3330f875f7e353fc65b5d3e6a Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:36:34Z rat: exlude anything under target/* commit 9af39d4e2548146422069374689d41b550d47c87 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:38:28Z Remove jsonld-comment commit aeff7c29e3022012cf313e845b94ea4c1f417af1 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:38:50Z 15s = 15000s, jna.nosys=true commit e499b1f1798e3e044570be199f5bb08fdec2f6f2 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:43:26Z Merge branch 'jena-osgi-tidy' into apache-jena-osgi commit 5bd3a24c7b7de8044fb558ff888c7ab526f73bcd Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:43:32Z Merge branch 'jena-osgi-NOTICE' into apache-jena-osgi commit ce26b3c2cb489c31eae9e14acb2608fcaca3371b Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:43:36Z Merge branch 'parent-rat-exclude-target' into apache-jena-osgi --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: NOTICE file for jena-osgi
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 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/22.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 #22 commit 5a89500065853f198e3b29b2c9d40d9c08e3c907 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:35:29Z NOTICE file for jena-osgi stripped version of apache-jena/NOTICE --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: rat: exlude anything under target/*
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-exclude-target Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/23.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 #23 commit 77e99e5e4cb6acf3330f875f7e353fc65b5d3e6a Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T17:36:34Z rat: exlude anything under target/* --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-878: Explicit imports of org.apache.xerces...
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 org.apache.xerces.impl classes we depend on. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-878-explicit-impl-imports Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/30.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 #30 commit 8d6a2cdfb348e3deab744b016f03e3e42aa67122 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-12T22:44:09Z 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 org.apache.xerces.impl classes we depend on. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-878 Avoid exposing xerces.impl.dv
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 of `org.apache.xerces.impl.dv`. This patch makes any method signature that involves org.apache.xerces.impl.dv package-private, e.g. those sending around `ValidationInfo`. This meant moving `XSDGenericType` to become an inner class of XSDDatatype. It could in theory be a separate class in the same package - but it shouldn't really be exposed or promoted - so I thought it was better to hide it in plain sight inside XSDDatatype which is the only class using it directly. I suggested now for `XSDDatatype.XSDGenericType` remains public as the other `impl.XSD*` classes are public - I guess they could be used mainly for `instanceof` checks? If not the class itself can also be made package-private or even private. This removes these particular warnings from jena-osgi about `org.apache.xerces.impl.dv`: ``` [WARNING] Bundle org.apache.jena:jena-osgi:bundle:2.13.0-SNAPSHOT : Export com.hp.hpl.jena.datatypes.xsd, has 1, private references [org.apache.xerces.impl.dv], [WARNING] Bundle org.apache.jena:jena-osgi:bundle:2.13.0-SNAPSHOT : Export com.hp.hpl.jena.datatypes.xsd.impl, has 1, private references [org.apache.xerces.impl.dv], ``` You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-878-avoid-exposing-impl Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/31.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 #31 commit 8d6a2cdfb348e3deab744b016f03e3e42aa67122 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-12T22:44:09Z 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 org.apache.xerces.impl classes we depend on. commit 830b9c30223b2d2f4a4a7732821e1b41fee2467f Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-13T00:00:34Z JENA-878 Not exposing xerces.dv.impl in method signatures commit 077c6ef71fe469884b830366fac60a60caf4ca9b Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-13T00:07:17Z JENA-878: XSDGenericType now inner class of XSDDatatype .. the only one who one would think needs to construct using xerces.impl.dv.XSSimpleType (via loadUserDefined) XSDGenericType now has a package-protected constructor as well to avoid leaking its XSSimpleDV outside this package. It was in com.hp.hpl.jena.datatypes.xsd.impl. before, so removing this is allowed given a new minor version number. comments used to say: This class is probably now redundant in that XSDDatatype can support run time conversion of union results. Left in for now during restructuring and in case any existing user code expects this type - very unlikely. commit 1c7455bbf1e162eebfb87f67e7df3ec82331916d Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-13T00:14:47Z JENA-878: Updated javadocs on XSDGenericType --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Javadoc rdf lang links
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 request into a Git repository by running: $ git pull https://github.com/stain/jena javadoc-rdf-lang-links Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/19.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 #19 commit 615dc55e798a2cf7cda9af3aa4e9ac1c2bdc4c6c Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T13:23:59Z Updated link to nquads commit a544ff5d3de38ed825c956d293c90d7c7c0d88d2 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T13:25:32Z Ntriples link commit 4cc6efb9b130dfb10de445bd155053c708167542 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T13:26:20Z Turtle link commit d46d67542713d2ecf9ecf16ad9e08560176485b3 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T13:26:59Z TriG link commit 209d1eeeaa8d948a3f75c4b1a27f65637b0a0b29 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T13:28:00Z RDF/XML link commit a9fbc060e25c91e4a5ced602aa9a5a854515503a Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T13:28:40Z RDF-JSON link commit b839394ecea14bbe35a4870fb62592cc1be8773d Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T13:33:24Z RDF/XML 1.1 link --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Fuseki2: Add JSON-LD, N-Triples to Content Typ...
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 fuseki2-more-graph-types Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/20.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 #20 commit dde2ee9bbebc2ee72f3c3ddfc6bb83f4eb120a4e Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T16:14:09Z Adds JSON-LD, N-Triples to Content Type dropdown .. and XML - RDF/XML --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Create iri from uri
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 d0c4669. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena create-iri-from-uri Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/18.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 #18 commit 56e1fdff987eafd3a123f20f00e2ad875e12b1a5 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-12T00:50:38Z Added IRIFactoryI.create(java.net.URI) commit d0c4669a04cdb208759c888d1f0af1520538461e Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-12T00:51:27Z Probably no need for uri.isAbsolute() special case --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Quieter jena-osgi-test logging
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 `LATEST` version for jena-osgi You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena jena-osgi-test-logging Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/28.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 #28 commit f4495f7334a87cd3ff8b6577b05cb1d890b7aadb Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-10T11:04:58Z pom.xml tab/space tidy commit 7279de49878669c60255d2f32553364940fe8659 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-10T11:58:43Z Reduce PAX logging commit dc540f9fcac76c5af1c7b7e060f22a879c29285e Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-10T11:59:52Z Look up jena-osgi version through system property --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Jena osgi integration test
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 into a Git repository by running: $ git pull https://github.com/stain/jena jena-osgi-integration-test Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/29.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 #29 commit be81eeba4d2eaf4d64c9d9a25f11862856894efa Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-10T13:15:50Z jena-osgi-test compile+test only in integration phase .. avoids compile errors on mvn clean test commit 5bbf8c73b95e35ee90d00be50cb04ca8ea8f160f Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-10T13:18:43Z name changed to Apache Jena OSGi integration tests --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Guava as shaded dependency
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](https://issues.apache.org/jira/browse/JENA-901). As this means `jena-core` gets a new dependencies (even our own!), and we have been shot down before for adding those in patch releases, this means a new minor version on anything from `jena-core` and downstream. I did not use this shaded jar within Elephas as it does not itself use Guava - Elephas does however have conflicting version dependencies on Guava 11.0.2 (from provided hadoop-common 2.6.0), 16.0.1 (from curator-client) and 18.0 (from airline dependency in jena-elephas-stats). I therefore changed `jena-elephas` outdated dependencyManagement on 11.0.2 to [18.0,) -- although this could be reduced to 16 as jena-elephas-stats is a demo-app and it can upgrade to 18 locally in its own pom (ideally airline etc. should themselves use ranges) You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena guava Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/45.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 #45 commit 623543a6c31a255d83be0bdb525c09a2f7fd0fac Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:13:49Z jena-shadowed-ext containing guava 18.0 commit e8b53617dbb23eedb335a4f2ef3677e9607d1f00 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:24:22Z Ignore dependency-reduced-pom.xml Setting dependencyReducedPomLocationtarget/dependency-reduced-pom.xml might also work, but see https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#dependencyReducedPomLocation commit a0a75f46dbef59cf389cb1a53c5ed345ca63bd21 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:25:27Z Bump minor versions as jena-core gains a dependency commit 07b65e0f1e6024a0e9735e5ab497aae349d3f70b Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:27:41Z typo --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-904 Avoid activeInterpreters leak
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 CCPF.close() is called through super.close() calls of its owners. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-904-LPBRuleEngine-leak Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/46.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 #46 commit 72a8d46419e1884d9969ba534992c88c98510a9d Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-21T02:14:49Z JENA-904 test LPDRuleEngine leak of activeInterpreters commit 0d3def3a08c263f3bba8bfbeb45725f18b1aa5ac Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-21T02:15:13Z JENA-904: Propagate .close() to generator commit e8d8df84c0b7d23447b2cdd977d63da4e2a2b340 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-21T02:18:35Z JENA-904 a bit more super.close() safest to call child.close() before your own super.close commit 7761edcd4f4bee881f53f002e0a33d486cc43fc1 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-21T02:30:07Z JENA-904: close the generator.interpreter only .. so that it is removed from activeInterpreters calling .setComplete() on the other hand broke other tests as it closes too much too early --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-901 Use Guava for cache, shadowed in jena-...
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 as a patch-version update - but at the downside that `jena-core` have to do import com.google.common.cache.Cache directly - while all other Jena modules would have to use import org.apache.jena.impl.ext.com.google.common.cache.Cache as it is shadowed with the JAR. This will cause problems in the other modules in an Eclipse-like environment, as the IDE will re-expose com.google version if `jena-core` is open - and they would then seemingly not be able to find the `oaj.impl.ext.*` version as that only exist in the Maven-built JAR. In this scenario, it would probably be cleaner for the other modules to also shadow guava - in addition to the space-wastage, this probably becomes a bit awkward - it also means you can't pass any Guava structures between Jena modules. One advantage however is that if they all shadow individually, then they can shadow with the [minimizeJar](https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#minimizeJar) option to only get the few Guava classes used (e.g. in jena-core only the Cache). You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-901-guava-only-jenacore Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/48.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 #48 commit fa020df5320ec2aaaeec29aa568352bca5022347 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-21T02:51:28Z JENA-901 Use Guava for cache, shadowed in jena-core this avoids adding a new module, so this is acceptable as a patch-version update. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-901 LPDRuleEngine cache Guava from jena-sh...
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 `org.apache.jena.ext.com.google.common.cache.Cache`. The considerations of #45 apply here - so because `jena-core` gets a new dependency `jena-shadowed-ext` - even though that is our own brand new JAR - that should not go out as a patch-level upgrade, but forces a new minor version on pretty much everything jena-core and downstream. (We've been told of for adding dependencies in a patch before) See also a second pull request #48. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-901-guava Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/47.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 #47 commit 50511efc0e3cdeaee95ee7254483b1ea9c1f9fea Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T02:52:08Z JENA-901 A simple BoundedMap - based on LinkedHashMap commit 06abde7d170bdc76ac3f9a7ef4159bb625028cfe Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T02:52:30Z JENA-901 Use BoundedMap for tabledGoals cache configurable with system property jena.rulesys.lp.max_cached_tabled_goals commit 0b2e72b7d604940c5b084f026c437484856e929a Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T02:55:06Z JENA-901 Test saturation of tabledGoals commit 83d7e8cfdd50f3de849731bf56cadf1d1daec15c Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T03:53:02Z measure size of engine commit 938db892729d7f1849c0a6f71b27ebd4d1be3ff9 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T04:16:02Z more reset.. still uses lots of memory commit 3d01fffa0d9ab6ee34b7f0e8ac540a53f3bf22c3 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T16:23:36Z JENA-901 use a LinkedList instead of ArrayList for activeInterpreters. They could be closed in arbitrary order, and also this avoids a large ArrayList remaining after a big burst of concurrent queries. Simplify test. Check activeInterpreters is empty - this didn't happen as I had forgotten to call it.hasNext() (which any use of an iterator would normally do). Test now with MAX=1024 and 128M find() calls. commit 4bc846cd10f07cdce923e1c0597cac1273103cd9 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T16:31:26Z JENA-901 BoundedMap - BoundedLRUMap .. to point out that it's the least accessed entry that is pruned first commit a293eca312f031c421e04cc4c7571f1321548a22 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T22:16:51Z Not using java-sizeof for testing anymore commit 623543a6c31a255d83be0bdb525c09a2f7fd0fac Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:13:49Z jena-shadowed-ext containing guava 18.0 commit e8b53617dbb23eedb335a4f2ef3677e9607d1f00 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:24:22Z Ignore dependency-reduced-pom.xml Setting dependencyReducedPomLocationtarget/dependency-reduced-pom.xml might also work, but see https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#dependencyReducedPomLocation commit a0a75f46dbef59cf389cb1a53c5ed345ca63bd21 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:25:27Z Bump minor versions as jena-core gains a dependency commit 07b65e0f1e6024a0e9735e5ab497aae349d3f70b Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:27:41Z typo commit 0af6d343549e73fe79a71759774e4188d51e1b7d Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:42:50Z manage Guava version ranges I did not use this shaded jar within Elephas as it does not itself use Guava - Elephas does however have conflicting version dependencies on Guava 11.0.2 (from provided hadoop-common 2.6.0), 16.0.1 (from curator-client) and 18.0 (from airline dependency in jena-elephas-stats). I therefore changed jena-elephas outdated dependencyManagement on 11.0.2 to [18.0,) -- although this could be reduced to 16 as jena-elephas-stats is a demo-app and it can upgrade to 18 locally in its own pom (ideally airline etc. should themselves use ranges) commit 4544becf9cc48cc13e41df2dddafdfb09e4560ec Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:45:17Z jena-shadowed-ext dependency .. to be used by JENA-901 commit 01fd71cee73a9a04f9d936aaea9448cd5547aa0e Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T23:51:09Z jena
[GitHub] jena pull request: JENA-901 Upper bound on LPDRuleEngine cache
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. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-901-LPDRuleEngine-bound-cache Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/44.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 #44 commit 50511efc0e3cdeaee95ee7254483b1ea9c1f9fea Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T02:52:08Z JENA-901 A simple BoundedMap - based on LinkedHashMap commit 06abde7d170bdc76ac3f9a7ef4159bb625028cfe Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T02:52:30Z JENA-901 Use BoundedMap for tabledGoals cache configurable with system property jena.rulesys.lp.max_cached_tabled_goals commit 0b2e72b7d604940c5b084f026c437484856e929a Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T02:55:06Z JENA-901 Test saturation of tabledGoals commit 83d7e8cfdd50f3de849731bf56cadf1d1daec15c Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T03:53:02Z measure size of engine commit 938db892729d7f1849c0a6f71b27ebd4d1be3ff9 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-19T04:16:02Z more reset.. still uses lots of memory commit 3d01fffa0d9ab6ee34b7f0e8ac540a53f3bf22c3 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-20T16:23:36Z JENA-901 use a LinkedList instead of ArrayList for activeInterpreters. They could be closed in arbitrary order, and also this avoids a large ArrayList remaining after a big burst of concurrent queries. Simplify test. Check activeInterpreters is empty - this didn't happen as I had forgotten to call it.hasNext() (which any use of an iterator would normally do). Test now with MAX=1024 and 128M find() calls. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-897 Override java.io.tmpdir to write to ta...
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 into a Git repository by running: $ git pull https://github.com/stain/jena JENA-897-jdbc-tmp Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/41.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 #41 commit 494d9471147fb8299813e068cf7f95d3e3d0e156 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-10T01:07:17Z JENA-897 Override java.io.tmpdir to write to target/ .. instead of /tmp or %TEMP% --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-901 Upper bound on LPDRuleEngine cache
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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Re-enable jena-osgi-tests
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. I've added comments about this to the pom. Now that the OSGi tests were running correctly, this highlighted a problem from #45 in that Guava has an optional import on `sun.misc` which prevented starting, so I added that as optional in our shading (as it is in the upstream Guava `META-INF/MANIFEST.MF`). I also re-added the explicit `extensionstrue/extensions` as those were added as a workaround for Maven 3.0.2 (see #32). You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena osgi-tests-reenabled Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/49.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 #49 commit dd0593fb1fdb87ec1fb247bd611404f204b827ed Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-31T00:16:07Z Revert Remove duplicate surefire plugin This reverts commit 3199dd1020e2f6ac06d49f2a230e5f9faad48382. The surefire-plugin execution is needed to run the tests in a later phase, after the OSGi bundle has been created commit 60a07379220cf7e20e3c6c0769c8a3a4051ee97a Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-31T00:47:54Z pom: Document extensions and executions commit 820fb5e8b5b8eef319b9d2c3a4c65aa875505fb2 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-31T00:48:16Z Only optionally import sun.misc (coming from new dependency Guava) commit 1a5914e0f0bacc3185f79fbe228b81bb15a3 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-31T00:52:09Z re-enable extensions for bundle-plugin for older Mavens --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-871 upgrade yasr and yasqe
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. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-871-upgrade-yasr-and-yasqe Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/40.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 #40 commit 8c3f710ae346b94363b848d5994cf3cba543fa54 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-04T23:36:15Z Updated yasr 2.4.12 from http://cdn.jsdelivr.net/yasr/2.4.12/yasr.min.js http://cdn.jsdelivr.net/yasr/2.4.12/yasr.min.js.map http://cdn.jsdelivr.net/yasr/2.4.12/yasr.css commit 18c0c7aa3f3bc32ab9138f0b4bc59635fc1af65d Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-04T23:37:29Z Updated yasqe 2.3.9 From http://cdn.jsdelivr.net/yasqe/2.3.9/yasqe.min.css http://cdn.jsdelivr.net/yasqe/2.3.9/yasqe.min.js http://cdn.jsdelivr.net/yasqe/2.3.9/yasqe.min.js.map --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-867 - temporarily disable Active? tickbo...
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/stain/jena JENA-867-disable-active-tickbox Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/33.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 #33 commit a98806e1e0006218f766b64b93627a5d2d85891b Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-25T16:07:06Z JENA-867 - temporarily disable Active? tickboxes --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-869 Disable download button until it works...
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/stain/jena JENA-869-disable-remove-button Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/35.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 #35 commit f97ef4963984cb60da16017e7d8593b13a392327 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-25T16:34:27Z JENA-869 Disable download button until it works again --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Jena 887 remove dead links
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 to dataset.html instead of datasets.html) I didn't remove the server status link completely to keep the nice green icon - so now the link is just a non-functional anchor. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-887-remove-dead-links Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/36.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 #36 commit 275cf90e7143957803abdb2822a0635430f0a2d7 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-25T16:55:30Z JENA-887 Only links that work commit a5b55fa2125d706c4966e11bf7e67b8c1fc9fbc0 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-25T16:55:46Z JENA-887 Disable 'services' and 'server-log' links .. as they didn't work/exist commit 8b94a0f9d42854d28076686ee578c9d72a3f4a54 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-25T16:59:55Z JENA-887 admin/server-log file disabled --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-865: Include prefixes in example query
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 into a Git repository by running: $ git pull https://github.com/stain/jena JENA-865-example-query-prefixes Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/34.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 #34 commit b4e303ab286ffde9dbee65e9c9a504b5852c0776 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-25T16:18:01Z JENA-865: Include prefixes in example query --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-732 jena-maven-tools outputs to target/gen...
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/generated-sources/jena` according to Maven plugin conventions, instead of straight into `target/generated-sources`. (JENA-732) This also solves JENA-731 so that the source files are also compiled by Maven. I've therefore added tests to `src/it` to test for presence of the `*.class` files .. except for where `sources` configuration has been overridden as in [schemagen-integration-2](https://github.com/stain/jena/blob/JENA-732-reborn/jena-maven-tools/src/it/schemagen-integration-2/verify.bsh#L31) - but should it perhaps also add those sources to the compile path? Other plugins like jaxb-maven-plugin usually do.. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-732-reborn Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/37.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 #37 commit bdf57f582e4f55536d00932a7b057124516c59f8 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T00:32:29Z Revert JENA-731 JENA-732: revert pending dicussion. This reverts commit 8532f01f41a016cb9ea1d27bfc25c9e13e5f6bbc. commit f8a3b55793a12aa977015c8594fc81b2c0e26557 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T00:40:18Z JENA-732 Test generated source directory commit 9d791a273e02df931646b1ddce9b0b60e3e0c4f7 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T00:49:30Z JENA-731: Test that target/classes also compiled the classes Discuss: Should it still add to compile path when source was overriden? It currently does not.. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Jena 849 maven tools demo
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 into a Git repository by running: $ git pull https://github.com/stain/jena JENA-849-maven-tools-demo Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/38.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 #38 commit bdf57f582e4f55536d00932a7b057124516c59f8 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T00:32:29Z Revert JENA-731 JENA-732: revert pending dicussion. This reverts commit 8532f01f41a016cb9ea1d27bfc25c9e13e5f6bbc. commit f8a3b55793a12aa977015c8594fc81b2c0e26557 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T00:40:18Z JENA-732 Test generated source directory commit 9d791a273e02df931646b1ddce9b0b60e3e0c4f7 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T00:49:30Z JENA-731: Test that target/classes also compiled the classes Discuss: Should it still add to compile path when source was overriden? It currently does not.. commit 68d3b8a57190dfa8c198f254e9db28351c55b6fa Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T01:05:04Z JENA-731: document change of output default At the very least, this change should be documented in the changelog. commit b35e5389dcfa6f69960f898de1d5129722fca242 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T01:20:03Z JENA-732 outputDirectory - not output - to override commit 1b0088833bd7fa7bcac16a19463e38616aec8f88 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T01:25:08Z JENA-731 JENA-732 test custom outputDirectory .. and that it compiles commit a6db31dfc483d4ee3eec6a34c9df35a4d3561552 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-26T01:28:19Z JENA-849 Updated outdated jena-maven-tools/demo versions .. specially the new groupId/artifactId (why isn't it jena-maven-plugin ?) .. leaving pluginversion blank and RELEASE for jena-core. Ideally this should be proper versions updated by the release-plugin, but then we would need to change to multiple modules. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Guava as shaded dependency
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) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to You under the Apache License, Version 2.0 + (the License); you may not use this file except in compliance with + the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- + +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; + + modelVersion4.0.0/modelVersion + parent +groupIdorg.apache.jena/groupId +artifactIdjena-parent/artifactId +version13-SNAPSHOT/version +relativePath../jena-parent/relativePath + /parent + artifactIdjena-shadowed-ext/artifactId + version2.14.0-SNAPSHOT/version + packagingbundle/packaging + nameApache Jena - Shadowed external libraries/name + description +This module shadows some external libraries like Guava, +which we don't want to be depending on in their regular +package names, as they are likely to change/upgrade +externally and also be used in other libraries +in potentially conflicting versions. + +This module uses the Shade plugin to re-package them +under the package name +org.apache.jena.ext and is also a valid OSGi bundle +(but should only be used by used by other Jena modules). + + /description + + + dependencies +dependency + groupIdcom.google.guava/groupId + artifactIdguava/artifactId + !-- Version number specified explicitly and not in jena-parent, + as it should only be used here, and further shadowing/bundle/NOTICE + consideration might be needed on upgrade. -- + version18.0/version + !-- +As Guava does not contain a NOTICE and is also +licensed under Apache License, no additional +NOTICE is required by us. In a way we should probably +NOT include our own NOTICE file in this JAR.. + -- +/dependency + /dependencies + + build +plugins + plugin +groupIdorg.apache.maven.plugins/groupId +artifactIdmaven-shade-plugin/artifactId +executions + execution +phasepackage/phase +goals + goalshade/goal +/goals + /execution +/executions +configuration + artifactSet +includes + artifactcom.google.guava:guava/artifact +/includes + /artifactSet + relocations +relocation + patterncom.google/pattern + shadedPatternorg.apache.jena.ext.com.google/shadedPattern --- End diff -- `guava:18` is the only artifact that is selected to be shaded by the specified `includes` - so if that JAR contained other things under `com.google` (e.g. someone updates this to Guava 22 later) those would also be shaded. Is that not what we would want? Anyway, for consistency's sake (to match the bundle export), I've modified it to only include files under `com.google.common` and `com.google.thirdparty`. Note, transitives are not followed with the use of `includes`, so if the guava.pom started depending on other things, they would not get shaded. Alternatively I would need to use a different `parent` to avoid the dependencies` sneaking in from `jena-parent`, or try to keep matching `excludes` for those up to date here. The current dependency of guava includes only: ```xml dependency groupIdcom.google.code.findbugs/groupId artifactIdjsr305/artifactId optionaltrue/optional!-- needed only for annotations -- /dependency ``` I have updated the pull request to use explicit packages for `com.google.common` and `com.google.thirdparty`. --- If your project is set up for it, you can reply to this email and have your
[GitHub] jena pull request: JENA-901 Use Guava for cache, shadowed in jena-...
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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-909 - Docker image for Fuseki 2
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 that (thus it should also work for local snapshots, or download from Maven on demand). The Maven build does not make the docker image - and the readme now refers to stain/jena-fuseki (this should be changed to jena/jena-fuseki probably) You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena fuseki2-docker-maven Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/50.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 #50 commit e4d7fd9718b1a2f246f026fb860bc3bc5929c0f0 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-18T23:28:26Z Dockerfile for fuseki2 commit c71ab5bb1dae4b580fe0c6a083e147a2b75c1cdb Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-26T15:41:47Z Docker image for fuseki2 sets a random password if $ADMIN_PASSWORD is not set commit 0abec64f48da8b93543e440a6b5fbb894089c632 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-26T16:01:55Z Docker README commit 8941d0a0b9da2425b1d3bb1db083df0b7fd885ea Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-26T16:02:03Z clear /var/lib/apt* commit 64615f8dfba21eeabb32ec653ff95a6b8d9ca6b6 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-26T16:08:50Z include pwgen. entrypint sorted. commit 2b1d0e55b10748db6b2bb28e1e1b2f855f67c9b0 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-26T16:16:33Z Link to docker registry commit c2c512861948beb982d066e887f71422eae4f210 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-26T16:37:57Z Updated README commit 0c99ef91261c524422e49a99286460bba7456c11 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T13:48:32Z loader script commit 77ff337d9fadd61cdb85c5c0846edb7d5eb6f75b Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T14:16:49Z documentation commit 379221ce27ec190f5ce9deb4001639dd5a0f31e7 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T14:17:05Z Include tdbloader script commit 31cfd44948df62d5ff12b217178d1ba144b409ae Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T14:17:47Z tdbloader should not have --loc commit 252cdb1f85f2049dc542d00bc1bae6150f11f241 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T14:35:42Z Corrected path to ./tdbloader commit 6e9609dd803915aa4a5f9f4d5535b5ccb70ef74f Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T14:38:51Z simplify help - only if no arguments commit 4a462d47fcf71c044b7db0f97fd0ba41aa48292a Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T14:52:16Z databases/ commit 471d9c20e981c22b56aa67a21c0528583ddfa19c Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T15:36:01Z README: tdbloader details moved further down commit 7bd57b481815c954181f1470f7dd9181aab0fcf7 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T16:15:48Z README tweakery commit 3e914d21e2e645e9035c9af02fae440a77e7c1c9 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T16:16:55Z More README commit 7a0a6099e175a8e7654cad29764d29fad653b3f6 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T16:20:20Z Remember to stop fuseki first! commit d6dd0f476a6f2f5b69508255040d8bcd76243f17 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-27T16:23:34Z README correct paths within assembler file commit a05cc0da409ec6bd92e590451b95f18d51bba310 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T11:42:09Z About JVM_ARGS commit 120989eb2a5f7fbec01c637f5aa32587ced4de6f Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T11:43:05Z Include JVM_ARGS as well commit dcecd46d686c32c2bbe3100f020991911a641563 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T12:03:00Z Apache headers commit fdde1eae546429025ad559c6ed97fa77a866961f Author: Stian Soiland-Reyes st...@apache.org Date: 2015-01-28T12:41:53Z About changing ports, JENA-868 workaround. commit 00c48a0901c0a6dd2d105a61dc7735f73955e01e Author: Stian Soiland-Reyes st...@apache.org Date: 2015-02-02T10:03:06Z Use apache-jena-fuseki distribution commit 0a1c11a5e9bf43a626fc9cc22d03409f4ae40848 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-17T15:45:27Z Maven-based docker install commit 2a68d52c56e9e03f303debf89b94b196baaaff57 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-04-02T09:22:50Z JENA-909: Include jena-fuseki
[GitHub] jena pull request: Re-enable jena-osgi-tests
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 apache-jena-osgi) as the snapshot repository jena-osgi would not have the `sun.misc` patch. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Re-enable jena-osgi-tests
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` patch applied) - `mvn clean install` should work. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-1039: Avoid race-condition to OWL constant...
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: $ git pull https://github.com/stain/jena JENA-1039 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/93.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 #93 commit b1da86b0c3def6b9253639ad0d89563f2468d9bf Author: Stian Soiland-Reyes <st...@apache.org> Date: 2015-10-01T02:11:29Z JENA-1039: Avoid race-condition to OWL constants --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena issue #47: JENA-901 LPDRuleEngine cache Guava from jena-shadowed-ext
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 to investigate what is the semantic difference between the `LPInterpreter` constructor [without clauses](https://github.com/apache/jena/blob/master/jena-core/src/main/java/org/apache/jena/reasoner/rulesys/impl/LPInterpreter.java#L99) and [with clauses](https://github.com/apache/jena/blob/master/jena-core/src/main/java/org/apache/jena/reasoner/rulesys/impl/LPInterpreter.java#L111) (which could be [empty](https://github.com/apache/jena/blob/master/jena-core/src/main/java/org/apache/jena/reasoner/rulesys/impl/LPInterpreter.java#L130)) but then would not use `engine.getRuleStore().codeFor(goal)`. (Perhaps raise that as a new Jira issue?) --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-1139 workaround
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` from jena-osgi's inlined modules `jena-core`, `jena-arq` and `jena-tdb` You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-1139 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/126.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 #126 commit 2e0877898654d46e4d46efb0bcc3e84e0b94c7c1 Author: Stian Soiland-Reyes <st...@apache.org> Date: 2016-02-10T17:31:13Z JENA-1139 workaround This workaround concatinates the content of the other Jena modules src/main/resources/META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle from jena-osgi's inlined modules jena-core, jena-arq and jena-tdb --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-1169 Add Export Restriction READMEs
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://www.apache.org/dev/crypto.html#inform You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-1169 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/138.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 #138 commit 40b6daf9f513f78eb4f28c026deee7259e0bc054 Author: Stian Soiland-Reyes <soiland-re...@cs.manchester.ac.uk> Date: 2016-05-06T14:53:20Z Merge remote-tracking branch 'refs/remotes/apache/master' commit 8fedfdff40fbf0bb2687d472dd800a31a28c5b29 Author: Stian Soiland-Reyes <soiland-re...@cs.manchester.ac.uk> Date: 2016-05-06T15:18:04Z JENA-1169 Export Restriction notice Also this adds a basic README to the Fuseki binary distributions. TODO: Check if the READMEs also survive into the mvn release: source distribution. Highest-level README (e.g. what you would see on GitHub) reference the deeper READMEs. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Optional xerces bundle dependency
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 by running: $ git pull https://github.com/stain/jena xerces-dep Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/140.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 #140 commit 9dec22cdd5934400154773154966c6adb6c5 Author: Stian Soiland-Reyes <st...@apache.org> Date: 2016-05-09T12:38:31Z Optional xerces bundle dependency See also https://github.com/apache/jena/pull/134#issuecomment-209474708 of why this should be optional Related to #134 --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena issue #50: JENA-909 - Docker image for Fuseki 2
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 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena issue #50: JENA-909 - Docker image for Fuseki 2
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 it should automatically updated with a newer java arrives. I am a bit hampered trying to contribute to this as I am not a Jena committer and don't want to step on toes; after all, releasing Jena is the job of the PMC. I think this pull request is moot, it is very difficult to test it with the Docker build as part of the source build, as basically you will require a new compilation of the whole thing inside `Dockerfile`, or you would have to use a Maven plugin to build the Docker image (which would then require Docker installed). Jena already have a massive git repository which can take considerable time & disk to build, and I don't think it's right to add more to it. I think Jena and Fuseki should become two official images under the `_` namespace in Docker H hub - and then there should be a mini-git repository "jena-docker" - similar to [my jena-docker](https://github.com/stain/jena-docker) - but hosted under `apache/`, which could then be referenced from https://github.com/docker-library/official-images. That image will then simply pull the latest release from `dist.apache.org` and one only need to update version number and sha1 on any new release. As the binary is the same (just unpacked), no additional PMC release vote should be needed. Alternatively there could be a `jena` repository under https://github.com/docker-library/ managed by some PMC members. Obviously as such an image should be "official" I am unable to try to work on it in that way, as I am neither a committer nor on the PMC. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request #50: JENA-909 - Docker image for Fuseki 2
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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena issue #139: JSON-LD output
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 external retrieval of http://schema.org/ (but note that a download of the schema.org context is covered by http://creativecommons.org/licenses/by-sa/3.0/ ) --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request #189: JENA-1258 NodeFmtLib calls JenaSystem initializer
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 not normally find the bug ran from Maven as earlier tests would have caused initialization, but it can be tested from say Eclipse. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-1258 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/189.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 #189 commit 170f7e7f1e9634b3afae0a6bd14fc7c88f792b7b Author: Stian Soiland-Reyes <st...@apache.org> Date: 2016-11-07T01:20:25Z JENA-1258 NodeFmtLib initializer for JenaSystem.init --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena issue #189: JENA-1258 NodeFmtLib calls JenaSystem initializer
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 NodeFactory (and Node for legacy > reasons) only. I have tested this in a build. > > There is little point in a specific test because tests run in the overall > suite; it's almost confusing to have a test that doesn't. With > initialization in NodeFactory this will get tested anyway! > > Also, it would help to unroll ARQConstants (for RDF, RDFS, OWL, XSD) so it > does not need JenaSystem.init and then it is, with care, init-safe. > > See PR#192 for that all made real. > > The original example works when run separately to ensure minimal system > initialization. > > â > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/jena/pull/189#issuecomment-259124635>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAPd5fFN_RTsft_0zoh3lFvprRyNmYrsks5q8Gu3gaJpZM4Kqwha> > . > --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena issue #189: JENA-1258 NodeFmtLib calls JenaSystem initializer
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/apache/jena/riot/out/NodeFmtLib.html), and it is useful "outside" without much hazzle, then I don't see why it should be called "internal" just because it is also used internally. Agree that it would be good to ensure Jena initialization from `NodeFactory`. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena issue #203: JsonLDReader: possibility to override the @context
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 schema file in `src/test/resources/` - that would override the specified URL. A similar approach can be used with `src/main/resources` - but then of course you would have to keep the schema cache up to date, so that's more for the end application to do to avoid external network dependencies. Note that the actual [schema.org context file](http://schema.org/docs/jsonldcontext.json) is [licensed as CC BY SA](http://schema.org/docs/terms.html), but you could make a minimal version made just for the test which would not infringe copyright. --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena issue #413: JENA-1537: Remove dependency on Apache Xerces.
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] jena issue #413: JENA-1537: Remove dependency on Apache Xerces.
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 ourself" as Xerces is ASF. ---
[GitHub] jena pull request #341: JENA-1462: Tests RDF/XML parsing newer URI schemes
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 -- I included this to verify that the IRIs were acceptable for parsing overall, precisely as N-Triples has no base resolution. ---
[GitHub] jena pull request #341: JENA-1462: Tests RDF/XML parsing newer URI schemes
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 -- Commented in Java file, it was just to verify that it was not a UUID-like hostname that was causing the problem. It could be valid HTTP URL - with a local DNS search domain at least :) ---
[GitHub] jena pull request #341: JENA-1462: Tests RDF/XML parsing newer URI schemes
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 -- Should I still remove `*.nt`? For all we know future code might use different iri factories for relative resolution and NT/NQ parsing, as all the other formats use `file:///current/directory` as base by default. ---
[GitHub] jena pull request #341: JENA-1462: Tests RDF/XML parsing newer URI schemes
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> . --- End diff -- Removed *.nt tests in 5200369653704be86e24e6ce6d856369eec6 ---
[GitHub] jena pull request #341: JENA-1462: Tests RDF/XML parsing newer URI schemes
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 -- Bah, sorry.. silly me, I thought the comment was on http-base.rdf! Fixed in 33063f335d0cb9224a64dc2f77dbaa9963d92ecb `fileBaseRDF()` now passes after your JENA-1463 fix 1d037e80dfd8a91e9c4042f65695cadec4b17097 from #342 :-) -- only `fileRefRDF()` still fails (passing the base to `RDFDataMgr.read`) ```turtle <http://www.w3.org/2000/01/rdf-schema#seeAlso> . ``` ---
[GitHub] jena pull request #341: JENA-1462: Tests RDF/XML parsing newer URI schemes
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, such as `ssh://example.com/nested/`, fails. Note as JENA-1462 is not fixed by this PR, this only adds the unit tests and test files. This test also highlights a bug in parsing URIs like `file://example.com/etc/passwd` as described in [JENA-1463](https://issues.apache.org/jira/browse/JENA-1463) You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-1462 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/341.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 #341 commit 6ecd48af6967ca48f985850393ac3b16df31a314 Author: Stian Soiland-Reyes <stain@...> Date: 2018-01-11T18:12:33Z JENA-1462: Tests RDF/XML parsing newer URI schemes RIOT parsing RDF/XML with a base URI different from http/https/file, such as ssh://, fails. Note as JENA-1462 is not fixed, this only adds the unit tests. ---
