Re: Compile Forked Version

2017-01-08 Thread Samur Araujo
Hi Osma, I manage to compile all skipping the test cases. Indeed there is a little bug that needs to be fixed to make all work. https://github.com/apache/jena/commit/0cc1d1a01f0e9ce1656d48 ad5b93095b6cdea263 I had a hope that lucene 5.5.3 would be faster but fuseki is still slow. I will create

Re: Compile Forked Version

2017-01-07 Thread Osma Suominen
Hi Samur, At the time Jean-Marc worked on this (and I helped), it was evidently possible to compile it. IIRC what I did back then was not to compile everything, but just the modules that were changed, i.e. jena-text and jena-spatial, and then either jena-fuseki1 or jena-fuseki2. This way

Re: Compile Forked Version

2017-01-06 Thread Samur Araujo
Thank you for all the help! It is clear now that the fork have several bugs and issues. Best. On 6 January 2017 at 11:51, Andy Seaborne wrote: > > > On 05/01/17 16:16, Samur Araujo wrote: > >> Thank you Andy, your suggestion worked but I got this new error: >> > > Don't

Re: Compile Forked Version

2017-01-06 Thread Andy Seaborne
On 05/01/17 16:16, Samur Araujo wrote: Thank you Andy, your suggestion worked but I got this new error: Don't recognize that one and I don't remember it being some issue with Jena. It would be good if that clone yuo are workign from were up-to-date with the Jena development master branch

Re: Compile Forked Version

2017-01-06 Thread Lorenz B.
You could also try to do a rebase > Thank you Andy, your suggestion worked but I got this new error: > > NFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 8 resources > [INFO] Copying 1 resource > [INFO] Copying 3 resources > [INFO] > [INFO] ---

Re: Compile Forked Version

2017-01-05 Thread Samur Araujo
Thank you Andy, your suggestion worked but I got this new error: NFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 8 resources [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ jena-fuseki-core ---

Re: Compile Forked Version

2017-01-05 Thread Andy Seaborne
On 05/01/17 15:26, Samur Araujo wrote: <<< FAILURE! - in org.apache.jena.riot.tokens.TS_Tokens tokenUnit_iri18(org.apache.jena.riot.tokens.TestTokenizer) Time elapsed: 0.004 sec <<< ERROR! java.lang.Exception: Unexpected exception, expected but was at

Re: Compile Forked Version

2017-01-05 Thread A. Soroka
I get the same error. I don't think there is any problem with Maven here and you should not be spending time with Maven. The fork just doesn't build. You will have to take this up with the maintainer of that fork, Jean-Marc Vanel (jmvanel), and the dev@ list might be more appropriate at this

Re: Compile Forked Version

2017-01-05 Thread Samur Araujo
I follow your suggestion: --- T E S T S --- Running org.apache.jena.web.TS_Web Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.493 sec - in org.apache.jena.web.TS_Web Running

Re: Compile Forked Version

2017-01-05 Thread A. Soroka
If you have cloned that fork, try just doing a simple `mvn clean install` in the project root, then look in jena-fuseki2/apache-jena-fuseki/target. You should find a Fuseki distribution there with the forked code. --- A. Soroka The University of Virginia Library > On Jan 5, 2017, at 10:13 AM,

Re: Compile Forked Version

2017-01-05 Thread Samur Araujo
I want to run fuseki with lucene 5 or higher. There is a fork for it here : https://github.com/jmvanel/jena/commits/master I download it and I am trying to compile/package it. I did no change in the code of this fork. For know only trying to make it to work. Any suggestion? On 5 January 2017

Re: Compile Forked Version

2017-01-05 Thread A. Soroka
Can you explain a little more about what you are trying to do? When you say "compile a forked version of Jena", if you have actually forked the entire codebase, you should be able to just compile the entire codebase to get SNAPSHOT version artifacts of your forked code. Why are you trying to

Re: Compile Forked Version

2017-01-05 Thread Samur Araujo
I run the sequence of commands below but it still failures. mvn release:update-versions -DdevelopmentVersion=3.1.1-myfork-SNAPSHOT mvn clean mvn install -Pbootstrap mvn install -Pdev -DskipTests=true [INFO] [INFO] Building

Re: Compile Forked Version

2017-01-05 Thread Andy Seaborne
On 05/01/17 09:49, Rob Vesse wrote: As others have already noted in this thread you will need to do a mvn install rather than a package. Yes - it is looking for "jena-core/3.1.1-myfork-SNAPSHOT" as specificed in the jena-arq POM. Rob On 05/01/2017 07:45, "Samur Araujo"

Re: Compile Forked Version

2017-01-05 Thread Rob Vesse
As others have already noted in this thread you will need to do a mvn install rather than a package. Rob On 05/01/2017 07:45, "Samur Araujo" wrote: Hi Rob, I tried your approach but I got this error when packing: It still cannot solve the dependencies. Am I

Re: Compile Forked Version

2017-01-04 Thread Samur Araujo
Hi Rob, I tried your approach but I got this error when packing: It still cannot solve the dependencies. Am I missing any parameter? ~/tools/jena-master-forked/jena-arq$ mvn package [INFO] Scanning for projects... [INFO] [INFO]

Re: Compile Forked Version

2017-01-04 Thread Rob Vesse
Probably the easiest thing to do is to change the versions in all the pom.xml files to a custom version so it can only use locally installed artefacts because the version won’t exist anywhere else i.e. Even if it looks for it on the Internet it won’t find it. You can do this automatically like

Re: Compile Forked Version

2017-01-04 Thread Andy Seaborne
The other modules will look for jena-core. If you want a different one, then change the pom.xml files to name a different artifact. Andy On 04/01/17 15:41, Lorenz Buehmann wrote: You can specify the modules that you want to install or ignore mvn clean install -pl !jena-core should do

Re: Compile Forked Version

2017-01-04 Thread Lorenz Buehmann
You can specify the modules that you want to install or ignore mvn clean install -pl !jena-core should do the trick and omit jena-core On 04.01.2017 15:53, Samur Araujo wrote: > My forked version overwrite the dependencies. I do not want it to get the > jena-core from repository but look for

Re: Compile Forked Version

2017-01-04 Thread Samur Araujo
My forked version overwrite the dependencies. I do not want it to get the jena-core from repository but look for it locally, in the jena-master local folder structure. Is there any way to easily configure this? On 4 January 2017 at 15:03, Andy Seaborne wrote: > > "mvn clean

Re: Compile Forked Version

2017-01-04 Thread Andy Seaborne
"mvn clean install" On 04/01/17 13:17, Samur Araujo wrote: Hi all, how do I compile a forked version of Jena? What are the parameters I need to be passed to maven? I used "mvn package -o" But I got the error: Could not resolve dependencies. You will need to let it down dependencies at

Compile Forked Version

2017-01-04 Thread Samur Araujo
Hi all, how do I compile a forked version of Jena? What are the parameters I need to be passed to maven? I used "mvn package -o" But I got the error: Could not resolve dependencies. -- Senior Data Scientist Geophy www.geophy.com Nieuwe Plantage 54-55 2611XK Delft +31 (0)70 7640725 1 Fore