Hi Andy, Yes, I evaluated both emf4sw and emftriple for my needs (a PoC project that performs some model transformation using Eclipse EMF ATL. I just need the backend serialization to OWL RDF/XML). I quickly found out that neither will build out of the Git repo with modern tools and libraries (of course... 4 to 8y old... what to expect? 😉
While more recent indeed, emftriple is much more complex, bringing extra dependencies I can do without (it uses Tycho as well, but also Xtend, ...) It was easier for me to prune emf4sw down to the minimum required for my project (no need for Sesame, etc...) and update the resulting subset to Java 8 and the latest Jena API. My attempt to build Jena was precisely aimed at installing the required libraries in my local p2, to satisfy the requirements of my subset of emf4sw. I am still unsure why Jena won't build on my system... Thanks for your help so far 😊 -- Olivier. -----Original Message----- From: Andy Seaborne <[email protected]> Sent: Friday, January 24, 2020 8:15 AM To: [email protected] Subject: Re: Q: Jena 3.14.0 (3.15.0-SNAPSHOT) build issue On 23/01/2020 16:30, [email protected] wrote: > I did try that before attempting to build Jena from sources: > > <properties> > ... > <jena.version>3.14.0</jena.version> > ... > </properties> > > <dependencies> > <dependency> > <groupId>org.apache.jena</groupId> > <artifactId>apache-jena-libs</artifactId> > <type>pom</type> > <version>${jena.version}</version> > </dependency> > ... > <dependencies> > > I keep getting this error while building the project that depends on Jena: > > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: > com.emf4sw.rdf.jena.feature.feature.group 0.7.3.qualifier > [ERROR] Missing requirement: com.emf4sw.rdf.jena.feature.feature.group > 0.7.3.qualifier requires 'org.eclipse.equinox.p2.iu; org.apache.jena 3.14.0' > but it could not be found > > As that project appears to use Tycho to build installable units > (please excuse my limited knowledge of Eclipse plugin build; I am > trying to ramp up...), I also tried to use the dependency on Jena's > OSGI components instead of the libraries: From distant memory - Tycho doesn't use maven respositories, it uses "p2" respositories, which might be why com.emf4sw.rdf.jena is not part of the Apache Jena project But https://github.com/ghillairet/emf4sw says its is no longer development (and is 8y old) https://github.com/ghillairet/emftriple is newer ... only 4yo. > > <!-- > https://mvnrepository.com/artifact/org.apache.jena/jena-osgi --> > <dependency> > <groupId>org.apache.jena</groupId> > <artifactId>jena-osgi</artifactId> > <version>${jena.version}</version> > </dependency> > > ... and ended up in the same place. > > Thanks, > > -- Olivier. > > > > -----Original Message----- > From: Andy Seaborne <[email protected]> > Sent: Thursday, January 23, 2020 11:09 AM > To: [email protected] > Subject: Re: Q: Jena 3.14.0 (3.15.0-SNAPSHOT) build issue > > You don't need to build it - it comes ready built. > > If you have a maven or gradle setup, Eclipse will import all the artifacts, > and including the recursive dependencies. > > Write the POM file for your project, include the project in Eclipse as a > maven project and Eclipse will do the setup. > > Don't forget the "<type>pom</type>". > > Here's the essence of one I use: > > <?xml version="1.0" encoding="utf-8"?> > > <project ....> > > <modelVersion>4.0.0</modelVersion> > > <groupId>org.seaborne.myproject</groupId> > <artifactId>jena-workspace</artifactId> > <packaging>jar</packaging> > <version>0.0.0-SNAPSHOT</version> > > <description>AFS workspace</description> > > <properties> > <ver.jena>3.15.0-SNAPSHOT</ver.jena> > </properties> > > <dependencies> > > <dependency> > <groupId>org.apache.jena</groupId> > <artifactId>apache-jena-libs</artifactId> > <version>${ver.jena}</version> > <type>pom</type> > </dependency> > > .... rest of project .... > > > > > Andy > > On 23/01/2020 16:01, [email protected] wrote: >> Hi Andy, >> >> Thank you for the prompt answer! >> >> Yes, I did import the projects into Eclipse and tried to build from >> there as per >> https://jena.apache.org/tutorials/using_jena_with_eclipse.html >> I need the Jena API as a dependency to another Eclipse / Maven based >> project, and somehow the dependencies were not satisfied by the >> "Specifying Jena as a dependency" method presented at >> https://jena.apache.org/download/maven.html, so I am trying to build >> and get it installed in my local p2 instead... >> >> I just ran the build again, though, from the command line, on a >> freshly booted laptop without Eclipse started, and ended up in the >> exact same place... >> >> See the attached logfile or the two relevant highlights below: >> >> --------------------------------------------------------------------- >> [INFO] --- contract-test-maven-plugin:0.2.0:contract-test (default) @ >> jena-core --- [INFO] Processing package: org.apache.jena.assembler >> [INFO] Processing package: org.apache.jena.datatypes ... >> [INFO] Processing package: org.apache.jena.vocabulary [INFO] Skip >> filter: Not( Wildcard( Sensitive, *.test.* ) ) [INFO] Could not create >> Interface report class >> java.lang.IllegalArgumentException: No classes found in >> [org.apache.jena.assembler, org.apache.jena.datatypes, >> org.apache.jena.enhanced, org.apache.jena.graph, org.apache.jena.mem, >> org.apache.jena.n3, org.apache.jena.ontology, org.apache.jena.rdf, >> org.apache.jena.rdfxml, org.apache.jena.reasoner, >> org.apache.jena.shared, org.apache.jena.util, org.apache.jena.vocabulary] >> at org.xenei.junit.contract.tooling.InterfaceReport.<init> >> (InterfaceReport.java:166) >> at org.xenei.contracts.maven.ContractMojo.execute >> (ContractMojo.java:212) >> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo >> (DefaultBuildPluginManager.java:137) >> ... >> --------------------------------------------------------------------- >> >> Q: How severe is the error above? Build appears to ignore it and go on... >> >> And this TDB2 test error won't go away: >> >> --------------------------------------------------------------------- >> [INFO] Running org.apache.jena.tdb2.sys.TestDatabaseOps >> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: >> 22.36 s <<< FAILURE! - in org.apache.jena.tdb2.sys.TestDatabaseOps >> [ERROR] backup_1(org.apache.jena.tdb2.sys.TestDatabaseOps) Time elapsed: >> 1.567 s <<< FAILURE! >> java.lang.AssertionError: expected:<2> but was:<3> >> at >> > org.apache.jena.tdb2.sys.TestDatabaseOps.lambda$backup_1$19(TestDatabaseOps. >> java:188) >> at >> org.apache.jena.tdb2.sys.TestDatabaseOps.backup_1(TestDatabaseOps.java >> :186) >> >> [INFO] Running org.apache.jena.tdb2.sys.TestSys [INFO] Tests run: 1, >> Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in >> org.apache.jena.tdb2.sys.TestSys [INFO] Running >> org.apache.jena.tdb2.TestDatabaseMgr >> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >> 3.194 s - in org.apache.jena.tdb2.TestDatabaseMgr >> [INFO] Running org.apache.jena.tdb2.TestTDB2 [INFO] Tests run: 3, >> Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.435 s - in >> org.apache.jena.tdb2.TestTDB2 [INFO] Running >> org.apache.jena.tdb2.TestTDBFactory >> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >> 7.639 s - in org.apache.jena.tdb2.TestTDBFactory >> [INFO] >> [INFO] Results: >> [INFO] >> [ERROR] Failures: >> [ERROR] TestDatabaseOps.backup_1:186->lambda$backup_1$19:188 > expected:<2> >> but was:<3> >> [INFO] >> [ERROR] Tests run: 684, Failures: 1, Errors: 0, Skipped: 5 >> --------------------------------------------------------------------- >> >> >> Sincerely, >> >> -- Olivier Hurez-Martin. >> >> >> -----Original Message----- >> From: Andy Seaborne <[email protected]> >> Sent: Thursday, January 23, 2020 7:15 AM >> To: [email protected] >> Subject: Re: Q: Jena 3.14.0 (3.15.0-SNAPSHOT) build issue >> >> Looks like another process is also using the target/class area. >> >> Do you have an IDE running at the same time as Maven? >> Or another mavn build job? >> >> Eclipse, for example, can break a concurrent maven build if it does >> it's background refresh and decide to recompile some files. >> >> Andy >> >> On 22/01/2020 20:46, [email protected] wrote: >>> . forgot one more build error, holding me up! >>> >>> >>> >>> [INFO] --- contract-test-maven-plugin:0.2.0:contract-test (default) @ >>> jena-core --- >>> >>> [INFO] Processing package: org.apache.jena.assembler >>> >>> [INFO] Processing package: org.apache.jena.datatypes >>> >>> [INFO] Processing package: org.apache.jena.enhanced >>> >>> [INFO] Processing package: org.apache.jena.graph >>> >>> [INFO] Processing package: org.apache.jena.mem >>> >>> [INFO] Processing package: org.apache.jena.n3 >>> >>> [INFO] Processing package: org.apache.jena.ontology >>> >>> [INFO] Processing package: org.apache.jena.rdf >>> >>> [INFO] Processing package: org.apache.jena.rdfxml >>> >>> [INFO] Processing package: org.apache.jena.reasoner >>> >>> [INFO] Processing package: org.apache.jena.shared >>> >>> [INFO] Processing package: org.apache.jena.util >>> >>> [INFO] Processing package: org.apache.jena.vocabulary >>> >>> [INFO] Skip filter: Not( Wildcard( Sensitive, *.test.* ) ) >>> >>> [INFO] Could not create Interface report class >>> >>> java.lang.IllegalArgumentException: No classes found in >>> [org.apache.jena.assembler, org.apache.jena.datatypes, >>> org.apache.jena.enhanced, org.apache.jena.graph, org.apache.jena.mem, >>> org.apache.jena.n3, org.apache.jena.ontology, org.apache.jena.rdf, >>> org.apache.jena.rdfxml, org.apache.jena.reasoner, >>> org.apache.jena.shared, org.apache.jena.util, >>> org.apache.jena.vocabulary] >>> >>> at org.xenei.junit.contract.tooling.InterfaceReport.<init> >>> (InterfaceReport.java:166) >>> >>> at org.xenei.contracts.maven.ContractMojo.execute >>> (ContractMojo.java:212) >>> >>> at >>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo >>> (DefaultBuildPluginManager.java:137) >>> >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:210) >>> >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:156) >>> >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:148) >>> >>> at >>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje >>> c >>> t >>> (LifecycleModuleBuilder.java:117) >>> >>> at >>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje >>> c >>> t >>> (LifecycleModuleBuilder.java:81) >>> >>> at >>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThre >>> a dedBui lder.build (SingleThreadedBuilder.java:56) >>> >>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute >>> (LifecycleStarter.java:128) >>> >>> at org.apache.maven.DefaultMaven.doExecute >>> (DefaultMaven.java:305) >>> >>> at org.apache.maven.DefaultMaven.doExecute >>> (DefaultMaven.java:192) >>> >>> at org.apache.maven.DefaultMaven.execute >>> (DefaultMaven.java:105) >>> >>> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) >>> >>> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) >>> >>> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) >>> >>> 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:498) >>> >>> at >>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced >>> (Launcher.java:282) >>> >>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch >>> (Launcher.java:225) >>> >>> at >>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode >>> (Launcher.java:406) >>> >>> at org.codehaus.plexus.classworlds.launcher.Launcher.main >>> (Launcher.java:347) >>> >>> [INFO] >>> >>> >>> >>> >>> >>> From: [email protected] <[email protected]> >>> Sent: Wednesday, January 22, 2020 3:44 PM >>> To: '[email protected]' <[email protected]> >>> Subject: Q: Jena 3.14.0 (3.15.0-SNAPSHOT) build issue >>> >>> >>> >>> Hello, >>> >>> >>> >>> I hope this is the right forum for this type of question. >>> >>> Please redirect me to the proper media if not. >>> >>> >>> >>> Trying to build Jena 1.13.1, 1.14.0, then 1.15.0-SNAPSHOT on Windows >>> 10 Pro, Maven 3.6.1, Java 1.8, Eclipse 2019-12, following >>> instructions found at >>> >>> >>> >>> https://jena.apache.org/getting_involved/index.html >>> >>> >>> >>> I am running into multiple issues: >>> >>> >>> >>> * Broken <http://answers.semanticweb.com/tags/jena/> >>> answers.semanticweb.com link on the wiki page >>> https://jena.apache.org/help_and_support/index.html >>> >>> >>> >>> * Build fails on RAT checks: >>> >>> >>> >>> [ERROR] Failed to execute goal >>> org.apache.rat:apache-rat-plugin:0.12:check >>> (rat-checks) on project jena-tdb2: Too many files with unapproved >>> license: 2 >>> >>> Worked around by using the Maven option -Drat.skip=true >>> >>> >>> >>> * Jena TDB2 project Junit tests fails with: >>> >>> >>> >>> [INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @ >>> jena-tdb2 --- >>> >>> [INFO] >>> >>> [INFO] ------------------------------------------------------- >>> >>> [INFO] T E S T S >>> >>> [INFO] ------------------------------------------------------- >>> >>> [INFO] Running org.apache.jena.tdb2.assembler.TestTDBAssembler >>> >>> [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >>> 6.685 s - in org.apache.jena.tdb2.assembler.TestTDBAssembler >>> >>> . >>> >>> [INFO] Running org.apache.jena.tdb2.sys.TestDatabaseOps >>> >>> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: >>> 21.136 s <<< FAILURE! - in org.apache.jena.tdb2.sys.TestDatabaseOps >>> >>> [ERROR] backup_1(org.apache.jena.tdb2.sys.TestDatabaseOps) Time elapsed: >>> 1.55 s <<< FAILURE! >>> >>> java.lang.AssertionError: expected:<2> but was:<3> >>> >>> at >>> >> > org.apache.jena.tdb2.sys.TestDatabaseOps.lambda$backup_1$19(TestDatabaseOps. >>> java:188) >>> >>> at >>> org.apache.jena.tdb2.sys.TestDatabaseOps.backup_1(TestDatabaseOps.jav >>> a >>> :186) >>> >>> >>> >>> Circumvented by skipping the tests altogether. >>> >>> >>> >>> Thanks, >>> >>> >>> >>> * OHM. >>> >>> >>> >>> >
