Dear Jonathan, Decided to answer in smaller pieces while going over the several things addressed in your mail. This answer only covers build/startup related problems/questions.
(1) Relative Paths to Stanbol Parent POM On Sun, Nov 18, 2012 at 5:57 AM, Jonathan Hunt <[email protected]> wrote: > Greetings > > I'm new to Stanbol & Java. I'd appreciate any advice you can provide > regarding the following: > > Working from the instructions at > https://stanbol.apache.org/docs/trunk/tutorial.html > > BTW, on https://stanbol.apache.org/docs/trunk/tutorial.html the link to all > available components gives a 404 > https://stanbol.apache.org/docs/trunk/components.html > > On OS X 10.7.5, I can checkout the project and initiate a build, but maven > halts with a POM error. > > I resolved the pom errors with several path changes. > > 17:08:39 jonathan:~/Documents/HuntDesign/projects/stanbol $ svn diff . > Index: launchers/bundlelists/pom.xml > =================================================================== > --- launchers/bundlelists/pom.xml (revision 1410712) > +++ launchers/bundlelists/pom.xml (working copy) > @@ -23,7 +23,7 @@ > <groupId>org.apache.stanbol</groupId> > <artifactId>stanbol-parent</artifactId> > <version>2-SNAPSHOT</version> > - <relativePath>../parent</relativePath> > + <relativePath>../../parent</relativePath> > </parent> > > <groupId>org.apache.stanbol</groupId> > Index: commons/security/usermanagement/pom.xml > =================================================================== > --- commons/security/usermanagement/pom.xml (revision 1410712) > +++ commons/security/usermanagement/pom.xml (working copy) > @@ -23,7 +23,7 @@ > <groupId>org.apache.stanbol</groupId> > <artifactId>stanbol-parent</artifactId> > <version>2-SNAPSHOT</version> > - <relativePath>../../parent</relativePath> > + <relativePath>../../../parent</relativePath> > </parent> Wrong relative paths to the parent pom are easy to be overlooked during development as they only cause the build to fail on a clean new build. Should be fixed by http://svn.apache.org/viewvc?rev=1410840&view=rev Thanks for reporting! - - - (2) IntegrationTests error > > After changing the pom paths, the mvn install continued for some time until > integration tests failed. > "[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." > There is a small probability that the "httpqueryheaders" integration tests fail. This also happens from time to time on the Jenkins (Continuous Integration Server) and has todo with test requesting data from the dbpedia Entityhub Referenced Site before the data are fully initialized. So if one (or both) of those tests where failing it was most likely because of this. If an other test where failing, than it would be nice if you could provide the surefire reports located under "{stanbol-trunk}/integration-tests/target/surefire-reports". BTW: I was unable to reproduce you issue on my machine (Apache Maven 3.0.4, Java version "1.6.0_37", Max OS 10.8.2). - - - (3) Launcher Startup > Since I don't know how to resolve those failures I re-initiated the install > without tests per "mvn -DskipTests clean install" and this proceeded to > completion. > > However, at http://localhost:8080/ only /enhancer and /entityhub are > available. (Previously I installed IKS 7.0, and additional endpoints were > enabled in that instance (e.g. contenthub). Also the dbpediaLinking engine is > not available. > combinded with > Looking at the log, I wonder if this message is relevant: > "ERROR: Bundle org.apache.stanbol.enhancer.engines.refactor [110]: Error > starting > slinginstall:org.apache.stanbol.enhancer.engines.refactor-0.10.0-SNAPSHOT.jar > (org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.stanbol.enhancer.engines.refactor [110]: Unable to resolve 110.0: > missing requirement [110.0] package; > (&(package=org.apache.stanbol.ontologymanager.servicesapi.collector)(version>=0.10.0)(!(version>=1.0.0)))) > org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.stanbol.enhancer.engines.refactor [110]: Unable to resolve 110.0: > missing requirement [110.0] package; > (&(package=org.apache.stanbol.ontologymanager.servicesapi.collector)(version>=0.10.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:680)" This is expected when using the stable launcher '{stanbol-trunk}/launchers/stable'. This launcher only contains the Enhancer and Entityhub. This would explain why you are only seeing this two exceptions and also this exception is expected during startup as the Refactor Engine is included in the Stanble Launcher but is missing the dependencies to the OntologyManager and Rules components. However > I stopped the stanbol instance and tried the '"full" build. > java -Xmx1g -XX:MaxPermSize=256m -jar > full/target/org.apache.stanbol.launchers.full-0.10.0-SNAPSHOT.jar > instead, but got > "ERROR: Bundle org.apache.stanbol.enhancer.engines.refactor [110]: Error > starting > slinginstall:org.apache.stanbol.enhancer.engines.refactor-0.10.0-SNAPSHOT.jar > (org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.stanbol.enhancer.engines.refactor [110]: Unable to resolve 110.0: > missing requirement [110.0] package; > (&(package=org.apache.stanbol.ontologymanager.servicesapi.collector)(version>=0.10.0)(!(version>=1.0.0)))) > org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.stanbol.enhancer.engines.refactor [110]: Unable to resolve 110.0: > missing requirement [110.0] package; > (&(package=org.apache.stanbol.ontologymanager.servicesapi.collector)(version>=0.10.0)(!(version>=1.0.0)))" > this is not expected and indicates some issue with the ontology manager. But as with the integration tests I was also unable to reproduce this. Also a look at the Exported packages of the "org.apache.stanbol.ontologymanager.servicesapi" shows that this module correctly exports "org.apache.stanbol.ontologymanager.servicesapi.collector,version=0.10.0.SNAPSHOT" and also that "org.apache.stanbol.enhancer.engines.refactor" imports "org.apache.stanbol.ontologymanager.servicesapi.collector,version=0.10.0.SNAPSHOT from org.apache.stanbol.ontologymanager.servicesapi (123)" You can check that yourself via the Apache Felix Webconsole under http://localhost:8080/system/console/bundles Also the "http://localhost:8090/system/console/depfinder"; (packages) tab is useful to check for packages that cause errors like that (in your case org.apache.stanbol.ontologymanager.servicesapi.collector) Can you please validate this in your launcher. Especially if "org.apache.stanbol.ontologymanager.servicesapi" exports "org.apache.stanbol.ontologymanager.servicesapi.collector". best Rupert -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
