Hi Eric, The build of the trunk is currently unstable. The two referenced integration tests are expected to fail. See STANBOL-1188[1] for details. If you are looking for a "stable" version you should instead work on the release-0.12 branch [2]. This will be also used for the upcoming 0.12 release of Stanbol.
best Rupert [1] https://issues.apache.org/jira/browse/STANBOL-1188 [2] http://svn.apache.org/repos/asf/stanbol/branches/release-0.12/ On Wed, Nov 20, 2013 at 7:18 PM, Eric Scott <eric.d.sc...@att.net> wrote: > Some follow-up: > > I went ahead and blew away my entire .m2 directory and .cache, downloaded a > fresh copy of stanbol and did a mvn clean install again. The process ran to > completion, but the build failed: > > :-( > > Failed tests: > testSparqlConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest): > GET request to > http://localhost:8765/enhancer/sparql?query=PREFIX+enhancer%3A+%3Chttp%3A%2F%2Fstanbol.apache.org%2Fontology%2Fenhancer%2Fenhancer%23%3EPREFIX+rdfs%3A+++++%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23%3ESELECT+distinct+%3Fname+%3Fchain+WHERE+%7B%3Fchain+a+enhancer%3AEnhancementChain+.%3Fchain+rdfs%3Alabel+%3Fname+.%7DORDER+BY+ASC%28%3Fname%29: > expecting status 200 (content: <html>(..) > testEngineConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest): > GET request to http://localhost:8765/enhancer/engine: no match for regexp > '<j.0:hasEngine > rdf:resource="http://localhost:.*/enhancer/engine/dbpediaLinking"/>', > content=(..) > > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > (lots of successes) > --snip --- > [INFO] Apache Stanbol Stateles Webmodule Archetype ....... SUCCESS [0.237s] > [INFO] Apache Stanbol Enhancer Engine Archetype .......... SUCCESS [0.131s] > [INFO] Apache Stanbol Integration Tests .................. FAILURE > [6:12.937s] > [INFO] Apache Stanbol Reactor NG ......................... SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 26:36.433s > [INFO] Finished at: Wed Nov 20 10:06:24 PST 2013 > [INFO] Final Memory: 425M/727M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on > project org.apache.stanbol.integration-tests: There are test failures. > [ERROR] > [ERROR] Please refer to > /home/eric/Install/stanbol/integration-tests/target/surefire-reports for the > individual test results. > [ERROR] -> [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/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <goals> -rf :org.apache.stanbol.integration-tests > > > On 11/20/2013 09:14 AM, Eric Scott wrote: >> >> Thanks for your response Rupert! >> >> OK I did this: >> >> ~/.m2/repository/org/apache/clerezza/ext$ rm -f -r org.apache.jena.tdb/ >> >> then >> >> ~/Install/stanbol$ mvn clean install >> >> [INFO] Scanning for projects... >> >> [23347 lines later....] >> >> ------------------------------------------------------- >> T E S T S >> ------------------------------------------------------- >> Running org.apache.stanbol.it.OsgiConsoleTest >> 08:28:27,666 INFO JarExecutor:142 - Using >> /home/eric/Install/stanbol/integration-tests/target/launchdir as working >> directory >> 08:28:27,676 INFO JarExecutor:181 - Executing java -Xmx1g >> -XX:MaxPermSize=256m -Dorg.apache.stanbol.offline.mode=true >> -Dorg.apache.sling.commons.log.level=DEBUG -jar >> /home/eric/Install/stanbol/integration-tests/target/dependency/org.apache.stanbol.launchers.full-1.0.0-SNAPSHOT.jar >> -p 8765 >> 08:28:27,677 INFO StanbolTestBase:73 - Forked subprocess server listening >> to: http://localhost:8765 >> 08:28:27,711 INFO StanbolTestBase:103 - Will wait up to 180 seconds for >> server to become ready >> 20.11.2013 08:28:27.834 *INFO * [main] Setting >> sling.home=/home/eric/Install/stanbol/integration-tests/target/launchdir/stanbol >> (system property sling.home) >> 20.11.2013 08:28:27.835 *INFO * [main] Starting Apache Sling in >> /home/eric/Install/stanbol/integration-tests/target/launchdir/stanbol >> 20.11.2013 08:28:27.843 *INFO * [main] Checking launcher JAR in folder >> /home/eric/Install/stanbol/integration-tests/target/launchdir/stanbol >> 20.11.2013 08:28:27.857 *INFO * [main] Installing new launcher: >> jar:file:/home/eric/Install/stanbol/integration-tests/target/dependency/org.apache.stanbol.launchers.full-1.0.0-SNAPSHOT.jar!/resources/org.apache.sling.launchpad.base.jar, >> 2.4.0 (org.apache.sling.launchpad.base.jar.1384964907856) >> 20.11.2013 08:28:27.859 *INFO * [main] Loading launcher class >> org.apache.sling.launchpad.base.app.MainDelegate from >> org.apache.sling.launchpad.base.jar.1384964907856 >> 20.11.2013 08:28:27.878 *INFO * [main] Setting >> sling.launchpad=/home/eric/Install/stanbol/integration-tests/target/launchdir/stanbol >> 20.11.2013 08:28:27.879 *INFO * [main] Setting >> org.osgi.service.http.port=8765 >> 20.11.2013 08:28:27.879 *INFO * [main] Starting launcher ... >> 20.11.2013 08:28:27.882 *INFO * [main] HTTP server port: 8765 >> 08:28:28,163 INFO StanbolTestBase:178 - Got ConnectException at >> http://localhost:8765/ - will retry >> 08:28:28,364 INFO StanbolTestBase:178 - Got ConnectException at >> http://localhost:8765/ - will retry >> 08:28:28,765 INFO StanbolTestBase:178 - Got ConnectException at >> http://localhost:8765/ - will retry >> 08:28:29,566 INFO StanbolTestBase:178 - Got ConnectException at >> http://localhost:8765/ - will retry >> 08:28:31,168 INFO StanbolTestBase:178 - Got ConnectException at >> http://localhost:8765/ - will retry >> 08:28:34,605 INFO StanbolTestBase:156 - Got 404 at http://localhost:8765/ >> - will retry >> ERROR: Bundle org.apache.stanbol.commons.solr.extras.smartcn [127]: Error >> starting >> slinginstall:org.apache.stanbol.commons.solr.extras.smartcn-0.12.0-SNAPSHOT.jar >> (org.osgi.framework.BundleException: Unresolved constraint in bundle >> org.apache.stanbol.commons.solr.extras.smartcn [127]: Unable to resolve >> 127.0: missing requirement [127.0] package; >> (&(package=org.apache.stanbol.commons.solr.utils)(version>=0.12.0)(!(version>=1.0.0)))) >> org.osgi.framework.BundleException: Unresolved constraint in bundle >> org.apache.stanbol.commons.solr.extras.smartcn [127]: Unable to resolve >> 127.0: missing requirement [127.0] package; >> (&(package=org.apache.stanbol.commons.solr.utils)(version>=0.12.0)(!(version>=1.0.0))) >> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3443) >> at org.apache.felix.framework.Felix.startBundle(Felix.java:1727) >> at >> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1156) >> at >> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) >> at java.lang.Thread.run(Thread.java:724) >> ERROR: Bundle org.apache.stanbol.commons.solr.extras.kuromoji [131]: Error >> starting >> slinginstall:org.apache.stanbol.commons.solr.extras.kuromoji-0.12.0-SNAPSHOT.jar >> (org.osgi.framework.BundleException: Unresolved constraint in bundle >> org.apache.stanbol.commons.solr.extras.kuromoji [131]: Unable to resolve >> 131.0: missing requirement [131.0] package; >> (&(package=org.apache.stanbol.commons.solr.utils)(version>=0.12.0)(!(version>=1.0.0)))) >> org.osgi.framework.BundleException: Unresolved constraint in bundle >> org.apache.stanbol.commons.solr.extras.kuromoji [131]: Unable to resolve >> 131.0: missing requirement [131.0] package; >> (&(package=org.apache.stanbol.commons.solr.utils)(version>=0.12.0)(!(version>=1.0.0))) >> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3443) >> at org.apache.felix.framework.Felix.startBundle(Felix.java:1727) >> at >> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1156) >> at >> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) >> at java.lang.Thread.run(Thread.java:724) >> Nov 20, 2013 8:28:36 AM org.glassfish.jersey.server.ApplicationHandler >> initialize >> INFO: Initiating Jersey application, version Jersey: 2.2 2013-08-14 >> 08:51:58... >> Nov 20, 2013 8:28:37 AM org.glassfish.jersey.server.ApplicationHandler >> initialize >> INFO: Initiating Jersey application, version Jersey: 2.2 2013-08-14 >> 08:51:58... >> Nov 20, 2013 8:28:37 AM org.glassfish.jersey.server.ApplicationHandler >> initialize >> INFO: Initiating Jersey application, version Jersey: 2.2 2013-08-14 >> 08:51:58... >> Nov 20, 2013 8:28:37 AM org.glassfish.jersey.server.ApplicationHandler >> initialize >> INFO: Initiating Jersey application, version Jersey: 2.2 2013-08-14 >> 08:51:58... >> Nov 20, 2013 8:28:37 AM org.glassfish.jersey.server.ApplicationHandler >> initialize >> INFO: Initiating Jersey application, version Jersey: 2.2 2013-08-14 >> 08:51:58... >> Nov 20, 2013 8:28:37 AM org.glassfish.jersey.server.ApplicationHandler >> initialize >> INFO: Initiating Jersey application, version Jersey: 2.2 2013-08-14 >> 08:51:58... >> # >> # A fatal error has been detected by the Java Runtime Environment: >> # >> # SIGSEGV (0xb) at pc=0x00007f754d15294e, pid=20732, tid=140141522503424 >> # >> # JRE version: 7.0_25-b30 >> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 >> compressed oops) >> # Problematic frame: >> # J java.util.LinkedList.add(Ljava/lang/Object;)Z >> # >> # Failed to write core dump. Core dumps have been disabled. To enable core >> dumping, try "ulimit -c unlimited" before starting Java again >> # >> # An error report file with more information is saved as: >> # >> /home/eric/Install/stanbol/integration-tests/target/launchdir/hs_err_pid20732.log >> # >> # If you would like to submit a bug report, please include >> # instructions on how to reproduce the bug and visit: >> # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ >> # >> 08:29:24,355 INFO DefaultHttpClient:693 - I/O exception >> (java.net.SocketException) caught when processing request: Connection reset >> 08:29:24,355 INFO DefaultHttpClient:700 - Retrying request >> 08:29:24,356 INFO StanbolTestBase:178 - Got ConnectException at >> http://localhost:8765/ - will retry >> 08:29:24,356 ERROR JarExecutor:155 - Process execution >> failed:org.apache.commons.exec.ExecuteException: Process exited with an >> error: 134 (Exit value: 134) >> org.apache.commons.exec.ExecuteException: Process exited with an error: >> 134 (Exit value: 134) >> at >> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377) >> at >> org.apache.commons.exec.DefaultExecutor.access$200(DefaultExecutor.java:46) >> at >> org.apache.commons.exec.DefaultExecutor$1.run(DefaultExecutor.java:188) >> 08:29:29,357 INFO StanbolTestBase:178 - Got ConnectException at >> http://localhost:8765/ - will retry >> 08:29:34,358 INFO StanbolTestBase:178 - Got ConnectException at >> http://localhost:8765/ - will retry >> >> On 11/18/2013 02:26 AM, Rupert Westenthaler wrote: >>> >>> Hi Eric, >>> >>> Even that the message says that the JAR got deleted IMO this is most >>> likely be caused by a corrupted JAR file. >>> >>> The maven build process takes JARs from the local cache. So most >>> likely this cached version is corrupted as well. So you should try to >>> >>> 1. delete the locally cached version (typically stored in >>> ~/.m2/repository). The Jena TDB bundle (provides by Apache Clerezza) >>> is located under >>> '~/.m2/repository/org/apache/clerezza/ext/org.apache.jena.tdb/'. Just >>> delete this folder from the local repository. >>> 2. rebuild the Stanbol launcher you are using - this should trigger >>> maven to re-download the deleted module >>> 3. go to the /target folder and try to start the newly build launcher. >>> >>> hope this helps >>> best >>> Rupert >>> >>> >>> On Sun, Nov 17, 2013 at 4:32 PM, Eric Scott <eric.d.sc...@att.net> wrote: >>>> >>>> Hi all - >>>> >>>> I'm working through the getting-started instructions, and the >>>> installation >>>> seemed to have gone through without complaint, but when I try to fire up >>>> <http://localhost:8080/enhancer>, I get a 404 error, with the following >>>> message in the stack traces: >>>> >>>> eric > ~/Install/stanbol/launchers$ java -Xmx1g -jar >>>> stable/target/org.apache.stanbol.launchers.stable-*-SNAPSHOT.jar >>>> 17.11.2013 07:06:43.995 *INFO * [main] Setting >>>> sling.home=/home/eric/Install/stanbol/launchers/stanbol (system property >>>> sling.home) >>>> 17.11.2013 07:06:43.996 *INFO * [main] Starting Apache Sling in >>>> /home/eric/Install/stanbol/launchers/stanbol >>>> 17.11.2013 07:06:44.008 *INFO * [main] Checking launcher JAR in folder >>>> /home/eric/Install/stanbol/launchers/stanbol >>>> 17.11.2013 07:06:44.016 *INFO * [main] Existing launcher is up to date, >>>> using it: 2.4.0 (org.apache.sling.launchpad.base.jar) >>>> 17.11.2013 07:06:44.018 *INFO * [main] Loading launcher class >>>> org.apache.sling.launchpad.base.app.MainDelegate from >>>> org.apache.sling.launchpad.base.jar >>>> 17.11.2013 07:06:44.031 *INFO * [main] Setting >>>> sling.launchpad=/home/eric/Install/stanbol/launchers/stanbol >>>> 17.11.2013 07:06:44.032 *INFO * [main] Starting launcher ... >>>> 17.11.2013 07:06:44.034 *INFO * [main] HTTP server port: 8080 >>>> ERROR: Bundle org.apache.jena.tdb [98]: Unable to get module class path. >>>> (java.lang.RuntimeException: Unable to open JAR file, probably deleted: >>>> error in opening zip file) >>>> java.lang.RuntimeException: Unable to open JAR file, probably deleted: >>>> error >>>> in opening zip file >>>> at >>>> >>>> org.apache.felix.framework.cache.JarContent.openZipFile(JarContent.java:489) >>>> at >>>> org.apache.felix.framework.cache.JarContent.<init>(JarContent.java:63) >>>> at >>>> >>>> org.apache.felix.framework.cache.JarContent.getEntryAsContent(JarContent.java:275) >>>> at >>>> >>>> org.apache.felix.framework.ModuleImpl.calculateContentPath(ModuleImpl.java:595) >>>> at >>>> >>>> org.apache.felix.framework.ModuleImpl.initializeContentPath(ModuleImpl.java:546) >>>> at >>>> >>>> org.apache.felix.framework.ModuleImpl.getContentPath(ModuleImpl.java:532) >>>> at >>>> org.apache.felix.framework.ModuleImpl.access$800(ModuleImpl.java:71) >>>> . >>>> . >>>> . >>>> >>>> A similar error message appears a couple dozen times after that. >>>> >>>> Any help would be appreciated! >>>> >>>> Thanks, >>>> >>>> >>>> >>>> >>> >>> >> >> > -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
