Re: Jena OSGi pull request
On 03/02/15 00:46, Stian Soiland-Reyes wrote: Ouch.. seems like a bug in Maven (or more likely) this magic org.rzo.yajsw.os.posix.PosixProcess used by org.everit.osgi. I guess setting it manually with -Djna.nosys=true didn't help either? Another reason to have a quick look at the PAX Exam (JENA-879) - which I'm in the middle of now. It's much more complicated.. :-( On 2 February 2015 at 20:34, Andy Seaborne a...@apache.org wrote: -Djna.nosys=true Changes the error ... (deleting vast amount of my m2 repo does not help) (2 different traces below, 2 different JVMs: openjdk-8 with mvn -Djna.nosys=true and with java-8-oracle (with and without -D) ... bsd env NMON=cmdkV bsd env EXINIT=set ai aw warn bsd env XDG_VTNR=7 bsd env XDG_RUNTIME_DIR=/run/user/1000 bsd env HOME=/home/afs bsd env GNOME_KEYRING_PID=2785 /usr/lib/jvm/default-java/bin/java -Djna_tmpdir=/tmp/eosgi-363281406525354060-tmp -classpath /mnt/disk1/afs/m2/repo/org/rzo/yajsw/wrapper/11.11/wrapper-11.11.jar:/mnt/disk1/afs/m2/repo/net/java/dev/jna/jna/3.4.0/jna-3.4.0.jar -Dwrapperx.pipeStreams=true org.rzo.yajsw.os.posix.bsd.AppStarter ./runConsole.sh started process -1 exit code bsd process 1 Exception in thread main java.lang.Error: There is an incompatible JNA native library installed on this system. To resolve this issue you may do one of the following: - remove or uninstall the offending library - set the system property jna.nosys=true - set jna.boot.library.path to include the path to the version of the jnidispatch library included with the JNA jar file you are using at com.sun.jna.Native.clinit(Native.java:142) at org.rzo.yajsw.os.posix.PosixProcess$CLibrary.clinit(PosixProcess.java:60) at org.rzo.yajsw.os.posix.bsd.AppStarter.main(AppStarter.java:14) [ERROR] Error reading from input stream. Stopping redirection. java.io.IOException: Stream closed at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170) at java.io.BufferedInputStream.read(BufferedInputStream.java:336) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.everit.osgi.dev.maven.DaemonStreamRedirector$PollerRunnable.run(DaemonStreamRedirector.java:62) at java.lang.Thread.run(Thread.java:745) [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 19.186 s [INFO] Finished at: 2015-02-03T08:34:36+00:00 [INFO] Final Memory: 25M/284M [INFO] [ERROR] Failed to execute goal org.everit.osgi.dev:eosgi-maven-plugin:3.1.0:integration-test (integration-test) on project jena-osgi-test: Test Process of environment felix finished with exit code 1 - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [WARNING] Stopping test process: -1 bsd env XDG_RUNTIME_DIR=/run/user/1000 bsd env HOME=/home/afs bsd env GNOME_KEYRING_PID=2785 /usr/lib/jvm/java-8-oracle//bin/java -Djna_tmpdir=/tmp/eosgi-8727996463447348875-tmp -classpath /mnt/disk1/afs/m2/repo/org/rzo/yajsw/wrapper/11.11/wrapper-11.11.jar:/mnt/disk1/afs/m2/repo/net/java/dev/jna/jna/3.4.0/jna-3.4.0.jar -Dwrapperx.pipeStreams=true org.rzo.yajsw.os.posix.bsd.AppStarter ./runConsole.sh started process 6882 calling exec openjdk version 1.8.0_40-internal OpenJDK Runtime Environment (build 1.8.0_40-internal-b09) OpenJDK 64-Bit Server VM (build 25.40-b13, mixed mode) YAJSW: yajsw-stable-11.11 OS : Linux/3.16.0-28-generic/amd64 JVM : Oracle Corporation/1.8.0_40-internal//usr/lib/jvm/java-8-openjdk-amd64/jre/64 java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.rzo.yajsw.boot.WrapperExeBooter.main(WrapperExeBooter.java:43) Caused by: java.lang.Error: There is an incompatible JNA native library installed on this system. To resolve this issue you may do one of the following: - remove or uninstall the offending library - set the system property jna.nosys=true - set jna.boot.library.path to include the path to the version of the jnidispatch library included with the JNA jar file you are using at com.sun.jna.Native.clinit(Native.java:142) at
Re: Jena OSGi pull request
Uhm, well must admit I have no clue as to why JNA should be involved in the first place. If it happens on your machine on two JDKs I guess it could happen to anyone. I suggest was try to go with the alternative PAX test I made for JENA-879 instead, even if its not as maintainable https://github.com/stain/jena/tree/jena-osgi-pax-exam I just needs to check PAX' massive test dependency list for licensing issues, then I can put in the pull request. Not sure if PAX can test with multiple OSGi frameworks, in theory just adding a second dependency on say Equinox should work. On 3 Feb 2015 08:49, Andy Seaborne a...@apache.org wrote: On 03/02/15 00:46, Stian Soiland-Reyes wrote: Ouch.. seems like a bug in Maven (or more likely) this magic org.rzo.yajsw.os.posix.PosixProcess used by org.everit.osgi. I guess setting it manually with -Djna.nosys=true didn't help either? Another reason to have a quick look at the PAX Exam (JENA-879) - which I'm in the middle of now. It's much more complicated.. :-( On 2 February 2015 at 20:34, Andy Seaborne a...@apache.org wrote: -Djna.nosys=true Changes the error ... (deleting vast amount of my m2 repo does not help) (2 different traces below, 2 different JVMs: openjdk-8 with mvn -Djna.nosys=true and with java-8-oracle (with and without -D) ... bsd env NMON=cmdkV bsd env EXINIT=set ai aw warn bsd env XDG_VTNR=7 bsd env XDG_RUNTIME_DIR=/run/user/1000 bsd env HOME=/home/afs bsd env GNOME_KEYRING_PID=2785 /usr/lib/jvm/default-java/bin/java -Djna_tmpdir=/tmp/eosgi-363281406525354060-tmp -classpath /mnt/disk1/afs/m2/repo/org/rzo/yajsw/wrapper/11.11/ wrapper-11.11.jar:/mnt/disk1/afs/m2/repo/net/java/dev/jna/jna/3.4.0/jna-3.4.0.jar -Dwrapperx.pipeStreams=true org.rzo.yajsw.os.posix.bsd.AppStarter ./runConsole.sh started process -1 exit code bsd process 1 Exception in thread main java.lang.Error: There is an incompatible JNA native library installed on this system. To resolve this issue you may do one of the following: - remove or uninstall the offending library - set the system property jna.nosys=true - set jna.boot.library.path to include the path to the version of the jnidispatch library included with the JNA jar file you are using at com.sun.jna.Native.clinit(Native.java:142) at org.rzo.yajsw.os.posix.PosixProcess$CLibrary.clinit (PosixProcess.java:60) at org.rzo.yajsw.os.posix.bsd.AppStarter.main(AppStarter.java:14) [ERROR] Error reading from input stream. Stopping redirection. java.io.IOException: Stream closed at java.io.BufferedInputStream.getBufIfOpen( BufferedInputStream.java:170) at java.io.BufferedInputStream.read(BufferedInputStream.java:336) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.everit.osgi.dev.maven.DaemonStreamRedirector$ PollerRunnable.run(DaemonStreamRedirector.java:62) at java.lang.Thread.run(Thread.java:745) [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 19.186 s [INFO] Finished at: 2015-02-03T08:34:36+00:00 [INFO] Final Memory: 25M/284M [INFO] [ERROR] Failed to execute goal org.everit.osgi.dev:eosgi- maven-plugin:3.1.0:integration-test (integration-test) on project jena-osgi-test: Test Process of environment felix finished with exit code 1 - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ MojoExecutionException [WARNING] Stopping test process: -1 bsd env XDG_RUNTIME_DIR=/run/user/1000 bsd env HOME=/home/afs bsd env GNOME_KEYRING_PID=2785 /usr/lib/jvm/java-8-oracle//bin/java -Djna_tmpdir=/tmp/eosgi-8727996463447348875-tmp -classpath /mnt/disk1/afs/m2/repo/org/rzo/yajsw/wrapper/11.11/ wrapper-11.11.jar:/mnt/disk1/afs/m2/repo/net/java/dev/jna/jna/3.4.0/jna-3.4.0.jar -Dwrapperx.pipeStreams=true org.rzo.yajsw.os.posix.bsd.AppStarter ./runConsole.sh started process 6882 calling exec openjdk version 1.8.0_40-internal OpenJDK Runtime Environment (build 1.8.0_40-internal-b09) OpenJDK 64-Bit Server VM (build 25.40-b13, mixed mode) YAJSW: yajsw-stable-11.11 OS : Linux/3.16.0-28-generic/amd64 JVM : Oracle Corporation/1.8.0_40-internal//usr/lib/jvm/java-8-openjdk- amd64/jre/64 java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[jira] [Commented] (JENA-879) Use PAX Exam for jena-osgi-test
[ https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303120#comment-14303120 ] ASF GitHub Bot commented on JENA-879: - 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 Use PAX Exam for jena-osgi-test --- Key: JENA-879 URL: https://issues.apache.org/jira/browse/JENA-879 Project: Apache Jena Issue Type: Task Components: Build Affects Versions: Jena 2.13.0 Reporter: Stian Soiland-Reyes The eosgi plugin used by jena-osgi-test to run the tests within an OSGi container is licensed as LGPL. As an optional LGPL dependencies only used for running the test, this is nominally allowed within Apache, but this is a thin
[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. ---
[jira] [Commented] (JENA-879) Use PAX Exam for jena-osgi-test
[
https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303122#comment-14303122
]
Stian Soiland-Reyes commented on JENA-879:
--
License check for the test dependencies looks good:
* MIT license
* Eclipse Public License
* Apache license
* BSD license
{code}
Lists of 92 third-party dependencies.
(Apache Software License 2.0) A Swiss Army Knife for OSGi
(biz.aQute.bnd:bndlib:2.3.0 - http://www.aQute.biz/Code/Bnd/bndlib)
(GNU Lesser General Public License, Version 2.1) (The Apache Software
License, Version 2.0) Jackson-annotations
(com.fasterxml.jackson.core:jackson-annotations:2.3.0 -
http://wiki.fasterxml.com/JacksonHome)
(GNU Lesser General Public License, Version 2.1) (The Apache Software
License, Version 2.0) Jackson-core
(com.fasterxml.jackson.core:jackson-core:2.3.3 -
http://wiki.fasterxml.com/JacksonHome)
(GNU Lesser General Public License, Version 2.1) (The Apache Software
License, Version 2.0) jackson-databind
(com.fasterxml.jackson.core:jackson-databind:2.3.3 -
http://wiki.fasterxml.com/JacksonHome)
(Revised BSD License) JSONLD Java :: Core
(com.github.jsonld-java:jsonld-java:0.5.1 -
http://github.com/jsonld-java/jsonld-java/jsonld-java/)
(The Apache Software License, Version 2.0) Google Collections Library
(com.google.collections:google-collections:1.0 -
http://code.google.com/p/google-collections/)
(Unknown license) Codec (commons-codec:commons-codec:1.2 - no url defined)
(Apache License) HttpClient (commons-httpclient:commons-httpclient:3.1 -
http://jakarta.apache.org/httpcomponents/httpclient-3.x/)
(The Apache Software License, Version 2.0) Commons IO
(commons-io:commons-io:2.0.1 - http://commons.apache.org/io/)
(The Apache Software License, Version 2.0) Logging
(commons-logging:commons-logging:1.0.4 -
http://jakarta.apache.org/commons/logging/)
(Common Public License Version 1.0) JUnit (junit:junit:4.11 -
http://junit.org)
(The Apache Software License, Version 2.0) Apache Log4j
(log4j:log4j:1.2.17 - http://logging.apache.org/log4j/1.2/)
(The Apache Software License, Version 2.0) Apache Commons CSV
(org.apache.commons:commons-csv:1.0 -
http://commons.apache.org/proper/commons-csv/)
(The Apache Software License, Version 2.0) Apache Commons Lang
(org.apache.commons:commons-lang3:3.3.2 -
http://commons.apache.org/proper/commons-lang/)
(The Apache Software License, Version 2.0) Apache Felix Framework
(org.apache.felix:org.apache.felix.framework:4.6.0 -
http://felix.apache.org/org.apache.felix.framework/)
(Apache License) Apache HttpClient OSGi bundle
(org.apache.httpcomponents:httpclient-osgi:4.2.6 -
http://hc.apache.org/httpcomponents-client)
(Apache License) Apache HttpCore OSGi bundle
(org.apache.httpcomponents:httpcore-osgi:4.2.5 -
http://hc.apache.org/httpcomponents-core-ga)
(The Apache Software License, Version 2.0) Apache Jena - OSGi bundle
(org.apache.jena:jena-osgi:2.13.0-SNAPSHOT - http://jena.apache.org/)
(The Apache Software License, Version 2.0) Apache Log4j API
(org.apache.logging.log4j:log4j-api:2.0.2 -
http://logging.apache.org/log4j/2.x/log4j-api/)
(The Apache Software License, Version 2.0) Apache Log4j Core
(org.apache.logging.log4j:log4j-core:2.0.2 -
http://logging.apache.org/log4j/2.x/log4j-core/)
(The Apache Software License, Version 2.0) Maven Aether Provider
(org.apache.maven:maven-aether-provider:3.0.4 -
http://maven.apache.org/ref/3.0.4//maven-aether-provider)
(The Apache Software License, Version 2.0) Maven Artifact
(org.apache.maven:maven-artifact:3.0.5 -
http://maven.apache.org/ref/3.0.5//maven-artifact)
(The Apache Software License, Version 2.0) Maven Artifact Manager
(org.apache.maven:maven-artifact-manager:2.0.8 -
http://maven.apache.org/maven-artifact-manager)
(The Apache Software License, Version 2.0) Maven Core
(org.apache.maven:maven-core:3.0.5 -
http://maven.apache.org/ref/3.0.5//maven-core)
(The Apache Software License, Version 2.0) Maven Model
(org.apache.maven:maven-model:3.0.5 -
http://maven.apache.org/ref/3.0.5//maven-model)
(The Apache Software License, Version 2.0) Maven Model Builder
(org.apache.maven:maven-model-builder:3.0.4 -
http://maven.apache.org/ref/3.0.4//maven-model-builder)
(The Apache Software License, Version 2.0) Maven Plugin API
(org.apache.maven:maven-plugin-api:3.0.5 -
http://maven.apache.org/ref/3.0.5//maven-plugin-api)
(The Apache Software License, Version 2.0) Maven Plugin Registry Model
(org.apache.maven:maven-plugin-registry:2.0.8 -
http://maven.apache.org/maven-plugin-registry)
(The Apache Software License, Version 2.0) Maven Profile Model
(org.apache.maven:maven-profile:2.0.8 - http://maven.apache.org/maven-profile)
(The Apache Software License, Version 2.0) Maven Project Builder
[jira] [Commented] (JENA-879) Use PAX Exam for jena-osgi-test
[ https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303143#comment-14303143 ] Stian Soiland-Reyes commented on JENA-879: -- BTW - the external dependencies of the bundle are now listed explicitly in the PAX Exam test - we should put this as some kind of documentation of jena-osgi: https://github.com/stain/jena/blob/jena-osgi-pax-exam/jena-osgi-test/src/test/java/org/apache/jena/osgi/test/JenaOSGITest.java#L92 (I believe those alternative slf4j bindings are just needed to be compatible with PAX runner's logging -- but it might be relevant to others - see http://stackoverflow.com/questions/13308056/adding-osgi-fragment-bundles-in-felix-servletbridge-war ) Use PAX Exam for jena-osgi-test --- Key: JENA-879 URL: https://issues.apache.org/jira/browse/JENA-879 Project: Apache Jena Issue Type: Task Components: Build Affects Versions: Jena 2.13.0 Reporter: Stian Soiland-Reyes The eosgi plugin used by jena-osgi-test to run the tests within an OSGi container is licensed as LGPL. As an optional LGPL dependencies only used for running the test, this is nominally allowed within Apache, but this is a thin line, and it would be cleaner to avoid the dependency altogher - so that we can include jena-osgi-test in the general complete profile. http://mail-archives.apache.org/mod_mbox/jena-dev/201502.mbox/%3CCAPRnXtnf7Katv9mozKjr56nHjaqqGJnX8LpLZmyptae%2Bv9mD7g%40mail.gmail.com%3E An alternative (this task) is to use the PAX Exam system instead. (supposedly Apache licensed) It is probably good to allow jena-osgi-test to still test against multiple OSGi implementations as of today. Relevant links: https://ops4j1.jira.com/wiki/display/PAXEXAM4/Pax+Exam https://ops4j1.jira.com/wiki/display/PAXEXAM4/Getting+Started+with+OSGi+Tests https://ops4j1.jira.com/wiki/display/PAXEXAM4/OSGi+Containers Example use (possibly outdated): https://github.com/basis-technology-corp/tcl-regex-java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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. ---
Re: [GitHub] jena pull request: Apache jena osgi
I'm sorry, it is difficult to make a pull request be compatible with other pull request as I can't tell in advance the merge order, and I didn't want the file renames to go the wrong way around. If you want I can recreate #24 from scratch now that you have merged the #21 and #23. (Thank you!). You don't need the close #24 as I can do an evil git push --force. Or we can just let the dual-modules jena-osgi and jena-osgi-test stay for the 2.13.0 release. The idea of #24 was not to add a OSGi binary distribution build (although it would leave an obvious place for it), it just reorganized the modules as you suggested. So for NOTICE/LICENSE, we can do that as a separate thread, although I thought the stub from #22 would be sufficient for now as it covers exactly the content of the bundle JAR (*.jena, xerces and xml-apis), and the NOTICE file of apache-jena/ is also done manually. (which does lead to a maintenance problem, I agree). To generate NOTICE automatically by Maven can be done, but I'm not very skilled in the magic here - perhaps others know more. For jena-osgi the challenge is to play with those scopes so that it's picks up the correct licenses - we don't want to declare any NOTICE for say HTTP Components as that is an external dependency that is not included in the bundle binary. On 2 February 2015 at 19:23, Andy Seaborne a...@apache.org wrote: On 02/02/15 17:45, stain wrote: 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 Combined pull requests are harder to work with. They are extra work if not all the merged PRs are accepted without change. I'm pulling (and fixing up) #21 and #23 now and have just pushed them intot he Apache repo. #22 needs refining and discussion and it's very important (+ NOTICE doesn't look right to me and there is no LICENSE; maybe autogenerated works but that's yet more manual checking to do for a build that takes 30mins from clean). So I would need to unpick #24. Time consuming, which is why I asked not to do that. I'm sorry if I can't deal with these fast enough for you but the extra work in processing them, sending emails as well as having £work to do makes me slow. My ideal situation is to close #22 and #24 for now. We start with a new baseline of the repo as it is at this moment, post #21 and #23. We *discuss* what needs to be done for the NOTICE+LICENSE on dev@. You can PR a rename though I was hoping for other commentary on that as well. It might be easier to do after NL is done. Andy -- Stian Soiland-Reyes, eScience Lab School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/http://orcid.org/-0001-9842-9718
Re: [jira] [Commented] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE
I would expect it to delete it - you can create it from scratch, why
not completely delete it? It could be confusing if it reappars when
creating a new dataset with the same name.
In my case I wanted to wipe the dataset and start over - and didn't
expect the old data to reappear.
A Detach should be called that, not Remove/Delete.
It might matter from where the dataset came - was it made by hand in
the UI or came hard-coded in the config - which could be harder to
Delete.
On 3 February 2015 at 10:31, Andy Seaborne (JIRA) j...@apache.org wrote:
[
https://issues.apache.org/jira/browse/JENA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303051#comment-14303051
]
Andy Seaborne commented on JENA-869:
The first step is to define what Delete means. Is it remove from server?
Or is it delete the database entirely? I favour the former - Fuseki would
not remove the underlying database forever - so more like detach from
server.
Fuseki2: Can't reuse dataset name after DELETE
--
Key: JENA-869
URL: https://issues.apache.org/jira/browse/JENA-869
Project: Apache Jena
Issue Type: Bug
Components: Fuseki
Affects Versions: Fuseki 2.0.0
Environment: Docker
https://registry.hub.docker.com/u/stain/jena-fuseki/
Reporter: Stian Soiland-Reyes
Fix For: Fuseki 2.0.0
In the web interface, I create a persistent dataset test1. I then remove
it. I then create a second one called test1. Everything works fine.
However, if I restart Fuseki, now it attemps to register test1 twice:
{code}
[2015-01-28 12:47:33] ServletINFO Initializing Shiro environment
[2015-01-28 12:47:33] Config INFO Shiro file: file:///fuseki/shiro.ini
[2015-01-28 12:47:33] BuilderINFO Service: TDB test1
[2015-01-28 12:47:34] BuilderINFO Service: TDB test1
[2015-01-28 12:47:34] BuilderINFO Service: :service1
[2015-01-28 12:47:34] BuilderINFO Service: TDB test3
[2015-01-28 12:47:34] Config INFO Register: /test1
[2015-01-28 12:47:34] Config INFO Register: /test1
[2015-01-28 12:47:34] Server ERROR Exception in initialization: Already
registered: /test1
[2015-01-28 12:47:34] WebAppContext WARN Failed startup of context
o.e.j.w.WebAppContext@d04ca48{/,file:/jena-fuseki/webapp/,STARTING}
org.apache.jena.fuseki.FusekiException: Already registered: /test1
at
org.apache.jena.fuseki.server.DataAccessPointRegistry.register(DataAccessPointRegistry.java:28)
at
org.apache.jena.fuseki.server.FusekiServer.enable(FusekiServer.java:232)
at
org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints(FusekiServer.java:226)
at
org.apache.jena.fuseki.server.FusekiServerListener.init(FusekiServerListener.java:70)
at
org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized(FusekiServerListener.java:45)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:799)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.Server.start(Server.java:355)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
at org.eclipse.jetty.server.Server.doStart(Server.java:324)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.apache.jena.fuseki.jetty.JettyFuseki.start(JettyFuseki.java:137)
at
org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:331)
at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
at
org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:97)
at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
{code}
In the HTTP log from before:
{code}
[2015-01-28 12:47:02] Admin INFO [1] GET http://localhost:3031/$/server
[jira] [Commented] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE
[
https://issues.apache.org/jira/browse/JENA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303245#comment-14303245
]
Stian Soiland-Reyes commented on JENA-869:
--
(apologies for duplicate post - it seems emails don't go from dev@ and back to
Jira)
I would expect it to delete the folder as well - you can create it from
scratch, why not completely delete it? It could be confusing if it reappars
when creating a new dataset that just happens to have the same name (possibly
many months after deleting).
In my case I wanted to wipe the dataset and start over - and didn't expect the
old data to reappear.
A Detach feature should be called that, not Remove/Delete. (And anyway it
currently reattaches on restart :)
It might matter from where the dataset came - was it made by hand in the UI or
came hard-coded in the config - which could be harder to Delete.
Fuseki2: Can't reuse dataset name after DELETE
--
Key: JENA-869
URL: https://issues.apache.org/jira/browse/JENA-869
Project: Apache Jena
Issue Type: Bug
Components: Fuseki
Affects Versions: Fuseki 2.0.0
Environment: Docker
https://registry.hub.docker.com/u/stain/jena-fuseki/
Reporter: Stian Soiland-Reyes
Fix For: Fuseki 2.0.0
In the web interface, I create a persistent dataset test1. I then remove
it. I then create a second one called test1. Everything works fine.
However, if I restart Fuseki, now it attemps to register test1 twice:
{code}
[2015-01-28 12:47:33] ServletINFO Initializing Shiro environment
[2015-01-28 12:47:33] Config INFO Shiro file: file:///fuseki/shiro.ini
[2015-01-28 12:47:33] BuilderINFO Service: TDB test1
[2015-01-28 12:47:34] BuilderINFO Service: TDB test1
[2015-01-28 12:47:34] BuilderINFO Service: :service1
[2015-01-28 12:47:34] BuilderINFO Service: TDB test3
[2015-01-28 12:47:34] Config INFO Register: /test1
[2015-01-28 12:47:34] Config INFO Register: /test1
[2015-01-28 12:47:34] Server ERROR Exception in initialization: Already
registered: /test1
[2015-01-28 12:47:34] WebAppContext WARN Failed startup of context
o.e.j.w.WebAppContext@d04ca48{/,file:/jena-fuseki/webapp/,STARTING}
org.apache.jena.fuseki.FusekiException: Already registered: /test1
at
org.apache.jena.fuseki.server.DataAccessPointRegistry.register(DataAccessPointRegistry.java:28)
at
org.apache.jena.fuseki.server.FusekiServer.enable(FusekiServer.java:232)
at
org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints(FusekiServer.java:226)
at
org.apache.jena.fuseki.server.FusekiServerListener.init(FusekiServerListener.java:70)
at
org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized(FusekiServerListener.java:45)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:799)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.Server.start(Server.java:355)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
at org.eclipse.jetty.server.Server.doStart(Server.java:324)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.apache.jena.fuseki.jetty.JettyFuseki.start(JettyFuseki.java:137)
at
org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:331)
at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
at
org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:97)
at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
{code}
In the HTTP log from before:
{code}
[2015-01-28 12:47:02] Admin INFO [1] GET http://localhost:3031/$/server
[2015-01-28 12:47:02] Admin INFO [1] 200 OK (11 ms)
[2015-01-28
Re: [jira] [Commented] (JENA-626) SPARQL Query Caching
Hello Andy, I have build a prototype version for the SPARQL Query Cache implementation. I have provided the implementation details below: 1. Created CacheStore class with utility operation as doGet, doSet and doUnset cache. 2. Created CacheClient interface and implemented client for local in memory cache. 3. Created CacheAction class with enum fields as READ_CACHE and WRITE_CACHE. 4. Created Cache class as a wrapper object to hold the Cache result(Json result as of now) and SPARQLResultSet 5. I check in SPARQLQuery that if cache is null or is it initialised. 6. If it is null I set WRITE_CACHE action and pass cache object to ResponseResultSet. 7. ResponseResultSet creates a StringBuilder object and pass it to IndentedWriter. 8. As Query results are iterated and written in ServletOut Stream I also append the data in StringBuilder object. 9. Before flushing the data to Outstream I store the StringBuilder object which contain the json result in cache and set data in cache object has been initialised. 10. If CacheStore already contain the data then I retrieve the data from cache and write it to ServletOutStream and flush the data. Here are the code details in my jena fork. https://github.com/samaitra/jena/tree/master/jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/cache https://github.com/samaitra/jena/blob/master/jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/servlets/ResponseResultSet.java https://github.com/samaitra/jena/blob/master/jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/servlets/SPARQL_Query.java Please let me know your feedback. Currently I have tested the implementation with Ask and Select Queries. I still need to test it for Construct and Describe Queries. I will also need to make modification for returning thrift response. Regards Saikat On Sat, Jan 24, 2015 at 1:16 PM, Saikat Maitra saikat.mai...@gmail.com wrote: Thank you so much for your suggestion Andy. I have started working on 2a. Regards Saikat On Sat, Jan 24, 2015 at 1:38 AM, Andy Seaborne a...@apache.org wrote: Hello Claude, Andy, In reference to your email I would like to discuss the way I am looking forward to implement the Cache Layer. 1. We will be creating a global cache store based on config params passed via cache.properties. 2. Users will have option to select any of the following cache store as default a) In memory local cache b) remote in memory cache c) remote in memory cache with persistence in disk 3. We will update SPARQL_QUERY to read query results from cache if available and if the ResultSet is within valid time to live. 4. If cache has expired we will run executeQuery and repopulate the cache with updated time to live. 5. We will add Tests to validate different cache store operations. 6. I am still evaluating the changes required to accommodate different datasets. Please let me know if there are changes required in the implementation. Regards Saikat Hi Saikat, The plan looks good. One suggestion is to start simple. For example, get 2a working first, maybe with hardwired config, focus on getting that working end-to-end then go back and handle 2b and 2c and 1. By working on just one case, you'll validate the framework into which 2b and 2c have to fit. And it's nice to have something working as soon as possible :-) Tests - good! Andy
[jira] [Updated] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE
[
https://issues.apache.org/jira/browse/JENA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-869:
---
Description:
In the web interface, I create a persistent dataset test1. I then remove it.
I then create a second one called test1. Everything works fine.
However, if I restart Fuseki, now it attemps to register test1 twice:
{code}
[2015-01-28 12:47:33] ServletINFO Initializing Shiro environment
[2015-01-28 12:47:33] Config INFO Shiro file: file:///fuseki/shiro.ini
[2015-01-28 12:47:33] BuilderINFO Service: TDB test1
[2015-01-28 12:47:34] BuilderINFO Service: TDB test1
[2015-01-28 12:47:34] BuilderINFO Service: :service1
[2015-01-28 12:47:34] BuilderINFO Service: TDB test3
[2015-01-28 12:47:34] Config INFO Register: /test1
[2015-01-28 12:47:34] Config INFO Register: /test1
[2015-01-28 12:47:34] Server ERROR Exception in initialization: Already
registered: /test1
[2015-01-28 12:47:34] WebAppContext WARN Failed startup of context
o.e.j.w.WebAppContext@d04ca48{/,file:/jena-fuseki/webapp/,STARTING}
org.apache.jena.fuseki.FusekiException: Already registered: /test1
at
org.apache.jena.fuseki.server.DataAccessPointRegistry.register(DataAccessPointRegistry.java:28)
at
org.apache.jena.fuseki.server.FusekiServer.enable(FusekiServer.java:232)
at
org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints(FusekiServer.java:226)
at
org.apache.jena.fuseki.server.FusekiServerListener.init(FusekiServerListener.java:70)
at
org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized(FusekiServerListener.java:45)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:799)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.Server.start(Server.java:355)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
at org.eclipse.jetty.server.Server.doStart(Server.java:324)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.apache.jena.fuseki.jetty.JettyFuseki.start(JettyFuseki.java:137)
at
org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:331)
at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
at
org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:97)
at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
{code}
In the HTTP log from before:
{code}
[2015-01-28 12:47:02] Admin INFO [1] GET http://localhost:3031/$/server
[2015-01-28 12:47:02] Admin INFO [1] 200 OK (11 ms)
[2015-01-28 12:47:04] Admin INFO [2] GET http://localhost:3031/$/server
[2015-01-28 12:47:04] Admin INFO [2] 200 OK (1 ms)
[2015-01-28 12:47:08] Admin INFO [3] POST http://localhost:3031/$/datasets
[2015-01-28 12:47:08] Admin INFO [3] Create database : name = /test1
[2015-01-28 12:47:08] BuilderINFO Service: TDB test1
[2015-01-28 12:47:08] Admin INFO [3] 200 OK (499 ms)
[2015-01-28 12:47:09] Admin INFO [4] GET http://localhost:3031/$/server
[2015-01-28 12:47:09] Admin INFO [4] 200 OK (2 ms)
[2015-01-28 12:47:12] Admin INFO [5] POST http://localhost:3031/$/datasets
[2015-01-28 12:47:12] Admin INFO [5] Create database : name = /test2
[2015-01-28 12:47:12] BuilderINFO Service: :service1
[2015-01-28 12:47:12] Admin INFO [5] 200 OK (117 ms)
[2015-01-28 12:47:12] Admin INFO [6] GET http://localhost:3031/$/server
[2015-01-28 12:47:12] Admin INFO [6] 200 OK (3 ms)
[2015-01-28 12:47:16] Admin INFO [7] POST http://localhost:3031/$/datasets
[2015-01-28 12:47:16] Admin INFO [7] Create database : name = /test3
[2015-01-28 12:47:16] BuilderINFO Service: TDB test3
[2015-01-28 12:47:16] Admin INFO [7] 200 OK (126 ms)
[2015-01-28 12:47:16] Admin INFO [8]
[jira] [Commented] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE
[
https://issues.apache.org/jira/browse/JENA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303051#comment-14303051
]
Andy Seaborne commented on JENA-869:
The first step is to define what Delete means. Is it remove from server? Or
is it delete the database entirely? I favour the former - Fuseki would not
remove the underlying database forever - so more like detach from server.
Fuseki2: Can't reuse dataset name after DELETE
--
Key: JENA-869
URL: https://issues.apache.org/jira/browse/JENA-869
Project: Apache Jena
Issue Type: Bug
Components: Fuseki
Affects Versions: Fuseki 2.0.0
Environment: Docker
https://registry.hub.docker.com/u/stain/jena-fuseki/
Reporter: Stian Soiland-Reyes
Fix For: Fuseki 2.0.0
In the web interface, I create a persistent dataset test1. I then remove
it. I then create a second one called test1. Everything works fine.
However, if I restart Fuseki, now it attemps to register test1 twice:
{code}
[2015-01-28 12:47:33] ServletINFO Initializing Shiro environment
[2015-01-28 12:47:33] Config INFO Shiro file: file:///fuseki/shiro.ini
[2015-01-28 12:47:33] BuilderINFO Service: TDB test1
[2015-01-28 12:47:34] BuilderINFO Service: TDB test1
[2015-01-28 12:47:34] BuilderINFO Service: :service1
[2015-01-28 12:47:34] BuilderINFO Service: TDB test3
[2015-01-28 12:47:34] Config INFO Register: /test1
[2015-01-28 12:47:34] Config INFO Register: /test1
[2015-01-28 12:47:34] Server ERROR Exception in initialization: Already
registered: /test1
[2015-01-28 12:47:34] WebAppContext WARN Failed startup of context
o.e.j.w.WebAppContext@d04ca48{/,file:/jena-fuseki/webapp/,STARTING}
org.apache.jena.fuseki.FusekiException: Already registered: /test1
at
org.apache.jena.fuseki.server.DataAccessPointRegistry.register(DataAccessPointRegistry.java:28)
at
org.apache.jena.fuseki.server.FusekiServer.enable(FusekiServer.java:232)
at
org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints(FusekiServer.java:226)
at
org.apache.jena.fuseki.server.FusekiServerListener.init(FusekiServerListener.java:70)
at
org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized(FusekiServerListener.java:45)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:799)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.Server.start(Server.java:355)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
at org.eclipse.jetty.server.Server.doStart(Server.java:324)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.apache.jena.fuseki.jetty.JettyFuseki.start(JettyFuseki.java:137)
at
org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:331)
at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
at
org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:97)
at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
{code}
In the HTTP log from before:
{code}
[2015-01-28 12:47:02] Admin INFO [1] GET http://localhost:3031/$/server
[2015-01-28 12:47:02] Admin INFO [1] 200 OK (11 ms)
[2015-01-28 12:47:04] Admin INFO [2] GET http://localhost:3031/$/server
[2015-01-28 12:47:04] Admin INFO [2] 200 OK (1 ms)
[2015-01-28 12:47:08] Admin INFO [3] POST
http://localhost:3031/$/datasets
[2015-01-28 12:47:08] Admin INFO [3] Create database : name = /test1
[2015-01-28 12:47:08] BuilderINFO Service: TDB test1
[2015-01-28 12:47:08] Admin INFO [3] 200 OK (499 ms)
[2015-01-28 12:47:09] Admin INFO [4] GET http://localhost:3031/$/server
[jira] [Resolved] (JENA-876) Remove Elephas I/O module test debug output
[
https://issues.apache.org/jira/browse/JENA-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse resolved JENA-876.
Resolution: Fixed
Fix will be pushed shortly
Remove Elephas I/O module test debug output
---
Key: JENA-876
URL: https://issues.apache.org/jira/browse/JENA-876
Project: Apache Jena
Issue Type: Improvement
Components: Build
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Minor
Fix For: Jena 2.13.0
Apache Jena - Elephas - I/O
{noformat}
Tests run: 4, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0 sec - in
org.apache.jena.hadoop.rdf.io.input.bnodes.JsonLdTripleBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
/tmp/bnode_divergence2916843011349988169
/tmp/bnode_divergence791381644287808543
/tmp/bnode_identity6354179707572212418
/tmp/bnode_identity7385822480727158189
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
/tmp/bnode_divergence3568221187712367778
/tmp/bnode_divergence946753873793069649
/tmp/bnode_identity5684534458552577154
/tmp/bnode_identity3714227679468048929
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.436 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.TurtleBlankNodeTest
/tmp/bnode_divergence260851824420941984
/tmp/bnode_divergence6105034193229880561
/tmp/bnode_identity3574061403608987364
/tmp/bnode_identity4440441989773324488
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (JENA-876) Remove Elephas I/O module test debug output
[
https://issues.apache.org/jira/browse/JENA-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse reassigned JENA-876:
--
Assignee: Rob Vesse
Remove Elephas I/O module test debug output
---
Key: JENA-876
URL: https://issues.apache.org/jira/browse/JENA-876
Project: Apache Jena
Issue Type: Improvement
Components: Build
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Minor
Fix For: Jena 2.13.0
Apache Jena - Elephas - I/O
{noformat}
Tests run: 4, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0 sec - in
org.apache.jena.hadoop.rdf.io.input.bnodes.JsonLdTripleBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
/tmp/bnode_divergence2916843011349988169
/tmp/bnode_divergence791381644287808543
/tmp/bnode_identity6354179707572212418
/tmp/bnode_identity7385822480727158189
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
/tmp/bnode_divergence3568221187712367778
/tmp/bnode_divergence946753873793069649
/tmp/bnode_identity5684534458552577154
/tmp/bnode_identity3714227679468048929
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.436 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.TurtleBlankNodeTest
/tmp/bnode_divergence260851824420941984
/tmp/bnode_divergence6105034193229880561
/tmp/bnode_identity3574061403608987364
/tmp/bnode_identity4440441989773324488
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-877) Elephas Common API tests need log4j.properties
[
https://issues.apache.org/jira/browse/JENA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304391#comment-14304391
]
Rob Vesse commented on JENA-877:
The tests will naturally produce various output that is and should be at WARN
level even with an appropriate log4j configuration in place because the tests
include exercising functionality that has good reason to print warnings but
which don't in of themselves indicate any issue to be worried about
I will add an appropriate log4j configuration that routes the logging output
into a file under {{target/}} so that the output is captured if needed but
doesn't clutter the build output.
Elephas Common API tests need log4j.properties
--
Key: JENA-877
URL: https://issues.apache.org/jira/browse/JENA-877
Project: Apache Jena
Issue Type: Improvement
Components: Build
Affects Versions: Jena 2.13.0
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Trivial
{noformat}
Running org.apache.jena.hadoop.rdf.io.types.RdfTypesTest
{noformat}
{noformat}
Running org.apache.jena.hadoop.rdf.io.output.trig.BatchedTriGOutputTest
{noformat}
{noformat}
Running
org.apache.jena.hadoop.rdf.mapreduce.filter.TripleInvertedFilterByNoPredicateMapperTest
{noformat}
all give:
{noformat}
log4j:WARN No appenders could be found for logger (.).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{noformat}
Can we have a src/test/resources log4j/properties?
(scanning for WARN after a build to look for problems - helps if there are as
few WARN false-positives as possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (JENA-877) Elephas Common API tests need log4j.properties
[
https://issues.apache.org/jira/browse/JENA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse resolved JENA-877.
Resolution: Fixed
Elephas Common API tests need log4j.properties
--
Key: JENA-877
URL: https://issues.apache.org/jira/browse/JENA-877
Project: Apache Jena
Issue Type: Improvement
Components: Build
Affects Versions: Jena 2.13.0
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Trivial
{noformat}
Running org.apache.jena.hadoop.rdf.io.types.RdfTypesTest
{noformat}
{noformat}
Running org.apache.jena.hadoop.rdf.io.output.trig.BatchedTriGOutputTest
{noformat}
{noformat}
Running
org.apache.jena.hadoop.rdf.mapreduce.filter.TripleInvertedFilterByNoPredicateMapperTest
{noformat}
all give:
{noformat}
log4j:WARN No appenders could be found for logger (.).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{noformat}
Can we have a src/test/resources log4j/properties?
(scanning for WARN after a build to look for problems - helps if there are as
few WARN false-positives as possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (JENA-877) Elephas Common API tests need log4j.properties
[
https://issues.apache.org/jira/browse/JENA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse closed JENA-877.
--
Elephas Common API tests need log4j.properties
--
Key: JENA-877
URL: https://issues.apache.org/jira/browse/JENA-877
Project: Apache Jena
Issue Type: Improvement
Components: Build
Affects Versions: Jena 2.13.0
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Trivial
Fix For: Jena 2.13.0
{noformat}
Running org.apache.jena.hadoop.rdf.io.types.RdfTypesTest
{noformat}
{noformat}
Running org.apache.jena.hadoop.rdf.io.output.trig.BatchedTriGOutputTest
{noformat}
{noformat}
Running
org.apache.jena.hadoop.rdf.mapreduce.filter.TripleInvertedFilterByNoPredicateMapperTest
{noformat}
all give:
{noformat}
log4j:WARN No appenders could be found for logger (.).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{noformat}
Can we have a src/test/resources log4j/properties?
(scanning for WARN after a build to look for problems - helps if there are as
few WARN false-positives as possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (JENA-877) Elephas Common API tests need log4j.properties
[
https://issues.apache.org/jira/browse/JENA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-877:
---
Fix Version/s: Jena 2.13.0
Elephas Common API tests need log4j.properties
--
Key: JENA-877
URL: https://issues.apache.org/jira/browse/JENA-877
Project: Apache Jena
Issue Type: Improvement
Components: Build
Affects Versions: Jena 2.13.0
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Trivial
Fix For: Jena 2.13.0
{noformat}
Running org.apache.jena.hadoop.rdf.io.types.RdfTypesTest
{noformat}
{noformat}
Running org.apache.jena.hadoop.rdf.io.output.trig.BatchedTriGOutputTest
{noformat}
{noformat}
Running
org.apache.jena.hadoop.rdf.mapreduce.filter.TripleInvertedFilterByNoPredicateMapperTest
{noformat}
all give:
{noformat}
log4j:WARN No appenders could be found for logger (.).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{noformat}
Can we have a src/test/resources log4j/properties?
(scanning for WARN after a build to look for problems - helps if there are as
few WARN false-positives as possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (JENA-876) Remove Elephas I/O module test debug output
[
https://issues.apache.org/jira/browse/JENA-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-876:
---
Fix Version/s: Jena 2.13.0
Remove Elephas I/O module test debug output
---
Key: JENA-876
URL: https://issues.apache.org/jira/browse/JENA-876
Project: Apache Jena
Issue Type: Improvement
Components: Build
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Minor
Fix For: Jena 2.13.0
Apache Jena - Elephas - I/O
{noformat}
Tests run: 4, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0 sec - in
org.apache.jena.hadoop.rdf.io.input.bnodes.JsonLdTripleBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
/tmp/bnode_divergence2916843011349988169
/tmp/bnode_divergence791381644287808543
/tmp/bnode_identity6354179707572212418
/tmp/bnode_identity7385822480727158189
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
/tmp/bnode_divergence3568221187712367778
/tmp/bnode_divergence946753873793069649
/tmp/bnode_identity5684534458552577154
/tmp/bnode_identity3714227679468048929
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.436 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.TurtleBlankNodeTest
/tmp/bnode_divergence260851824420941984
/tmp/bnode_divergence6105034193229880561
/tmp/bnode_identity3574061403608987364
/tmp/bnode_identity4440441989773324488
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (JENA-877) Elephas Common API tests need log4j.properties
[
https://issues.apache.org/jira/browse/JENA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse reassigned JENA-877:
--
Assignee: Rob Vesse
Elephas Common API tests need log4j.properties
--
Key: JENA-877
URL: https://issues.apache.org/jira/browse/JENA-877
Project: Apache Jena
Issue Type: Improvement
Components: Build
Affects Versions: Jena 2.13.0
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Trivial
{noformat}
Running org.apache.jena.hadoop.rdf.io.types.RdfTypesTest
{noformat}
{noformat}
Running org.apache.jena.hadoop.rdf.io.output.trig.BatchedTriGOutputTest
{noformat}
{noformat}
Running
org.apache.jena.hadoop.rdf.mapreduce.filter.TripleInvertedFilterByNoPredicateMapperTest
{noformat}
all give:
{noformat}
log4j:WARN No appenders could be found for logger (.).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{noformat}
Can we have a src/test/resources log4j/properties?
(scanning for WARN after a build to look for problems - helps if there are as
few WARN false-positives as possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-877) Elephas Common API tests need log4j.properties
[
https://issues.apache.org/jira/browse/JENA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304394#comment-14304394
]
ASF subversion and git services commented on JENA-877:
--
Commit 322696e4553f8587c08de52559bda1d893d9fe45 in jena's branch
refs/heads/master from [~rvesse]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=322696e ]
Avoid log4j warnings in Elephas tests (JENA-877)
Adds a src/test/resources/log4j.properties in the relevant modules
Log output is captured under target/tests.log to avoid cluttering the
Maven build output
Elephas Common API tests need log4j.properties
--
Key: JENA-877
URL: https://issues.apache.org/jira/browse/JENA-877
Project: Apache Jena
Issue Type: Improvement
Components: Build
Affects Versions: Jena 2.13.0
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Trivial
{noformat}
Running org.apache.jena.hadoop.rdf.io.types.RdfTypesTest
{noformat}
{noformat}
Running org.apache.jena.hadoop.rdf.io.output.trig.BatchedTriGOutputTest
{noformat}
{noformat}
Running
org.apache.jena.hadoop.rdf.mapreduce.filter.TripleInvertedFilterByNoPredicateMapperTest
{noformat}
all give:
{noformat}
log4j:WARN No appenders could be found for logger (.).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{noformat}
Can we have a src/test/resources log4j/properties?
(scanning for WARN after a build to look for problems - helps if there are as
few WARN false-positives as possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (JENA-876) Remove Elephas I/O module test debug output
[
https://issues.apache.org/jira/browse/JENA-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse closed JENA-876.
--
Remove Elephas I/O module test debug output
---
Key: JENA-876
URL: https://issues.apache.org/jira/browse/JENA-876
Project: Apache Jena
Issue Type: Improvement
Components: Build
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Minor
Fix For: Jena 2.13.0
Apache Jena - Elephas - I/O
{noformat}
Tests run: 4, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0 sec - in
org.apache.jena.hadoop.rdf.io.input.bnodes.JsonLdTripleBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
/tmp/bnode_divergence2916843011349988169
/tmp/bnode_divergence791381644287808543
/tmp/bnode_identity6354179707572212418
/tmp/bnode_identity7385822480727158189
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
/tmp/bnode_divergence3568221187712367778
/tmp/bnode_divergence946753873793069649
/tmp/bnode_identity5684534458552577154
/tmp/bnode_identity3714227679468048929
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.436 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.TurtleBlankNodeTest
/tmp/bnode_divergence260851824420941984
/tmp/bnode_divergence6105034193229880561
/tmp/bnode_identity3574061403608987364
/tmp/bnode_identity4440441989773324488
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-876) Remove Elephas I/O module test debug output
[
https://issues.apache.org/jira/browse/JENA-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304393#comment-14304393
]
ASF subversion and git services commented on JENA-876:
--
Commit 3caffeb25ad40f8c3869c537ba3b0c3521cecdd9 in jena's branch
refs/heads/master from [~rvesse]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=3caffeb ]
Change debug output to actual log output not stdout (JENA-876)
Remove Elephas I/O module test debug output
---
Key: JENA-876
URL: https://issues.apache.org/jira/browse/JENA-876
Project: Apache Jena
Issue Type: Improvement
Components: Build
Reporter: Andy Seaborne
Assignee: Rob Vesse
Priority: Minor
Fix For: Jena 2.13.0
Apache Jena - Elephas - I/O
{noformat}
Tests run: 4, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0 sec - in
org.apache.jena.hadoop.rdf.io.input.bnodes.JsonLdTripleBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
/tmp/bnode_divergence2916843011349988169
/tmp/bnode_divergence791381644287808543
/tmp/bnode_identity6354179707572212418
/tmp/bnode_identity7385822480727158189
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.NTriplesBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
/tmp/bnode_divergence3568221187712367778
/tmp/bnode_divergence946753873793069649
/tmp/bnode_identity5684534458552577154
/tmp/bnode_identity3714227679468048929
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.436 sec -
in org.apache.jena.hadoop.rdf.io.input.bnodes.RdfJsonBlankNodeTest
Running org.apache.jena.hadoop.rdf.io.input.bnodes.TurtleBlankNodeTest
/tmp/bnode_divergence260851824420941984
/tmp/bnode_divergence6105034193229880561
/tmp/bnode_identity3574061403608987364
/tmp/bnode_identity4440441989773324488
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Jena OSGi pull request
On 03/02/15 09:07, Stian Soiland-Reyes wrote: then I can put in the pull request. BTW - if the PR comment has the string JENA-879 in it, then it should get referenced by the JIRA. After what seems like a few dropped emails, we seem to be back connected for github/asf emails so it would be good to verify that. Andy
