subject:"Re\: Compile Forked Version"

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 another thread to discuss the issue.

Best,

On 7 January 2017 at 14:14, Osma Suominen  wrote:

> 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 only
> the modified modules were manually built for the Fuseki build, with
> everything else coming from the Maven repositories. But of course, at the
> time, the fork was pretty much up to date with jena master and the Maven
> repository. Now it has already diverged and there was the 3.1.1 release in
> between, which affects the version numbers of all modules.
>
>
> I've created a git branch which takes the current jena master and rebases
> jmvanel's forked master on top of that:
> https://github.com/osma/jena/tree/lucene5
>
> I was able to build it like this:
>
> 1. Clear the local Maven repository (~.m2/repository) just in case
> 2. Run "mvn clean install" under jena-text
> 3. Run "mvn clean install" under jena-spatial
> 4. Run "mvn clean package" under jena-fuseki1
>
> The resulting Fuseki package under target/ should now contain the
> jena-text and jena-spatial modules built with Lucene 5.5.3.
>
>
> I tried building jena-fuseki2 too, but it failed with an error that I
> suspect is not related to the Lucene changes.
>
> Hope this helps,
> Osma
>
>
> 06.01.2017, 14:27, Samur Araujo wrote:
>
>> 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 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 so that the state of it is known.
>>>
>>> https://github.com/jmvanel/jena/commits/master
>>>
>>> is not the Jena projects code repository - as ajs6f says, you will have
>>> to
>>> take this up with the maintainer of that fork, Jean-Marc Vanel (jmvanel)
>>> and find out what the state of work there is.
>>>
>>> Andy
>>>
>>>
>>> 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 ---
 [INFO] Changes detected - recompiling the module!
 [INFO] Compiling 111 source files to
 /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
 core/target/classes
 [INFO]
 [INFO] --- maven-resources-plugin:2.7:testResources
 (default-testResources)
 @ jena-fuseki-core ---
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory
 /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
 core/src/test/resources
 [INFO] Copying 3 resources
 [INFO]
 [INFO] --- maven-compiler-plugin:3.5.1:testCompile
 (default-testCompile)
 @
 jena-fuseki-core ---
 [INFO] Changes detected - recompiling the module!
 [INFO] Compiling 19 source files to
 /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
 core/target/test-classes
 [INFO]
 [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
 jena-fuseki-core ---

 ---
  T E S T S
 ---
 Running org.apache.jena.fuseki.TS_Fuseki
 [2017-01-05 17:11:41] riot   ERROR [line: 6, col: 7 ] Unexpected
 attribute : :datatype at typedLiteral
 Exception in thread "Thread-73" org.apache.jena.riot.RiotException:
 [line:
 6, col: 7 ] Unexpected attribute : :datatype at typedLiteral
 at
 org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandler
 Std.error(ErrorHandlerFactory.java:128)
 at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
 at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
 at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
 at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
 at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
 at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
 at

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 
only the modified modules were manually built for the Fuseki build, with 
everything else coming from the Maven repositories. But of course, at 
the time, the fork was pretty much up to date with jena master and the 
Maven repository. Now it has already diverged and there was the 3.1.1 
release in between, which affects the version numbers of all modules.



I've created a git branch which takes the current jena master and 
rebases jmvanel's forked master on top of that:

https://github.com/osma/jena/tree/lucene5

I was able to build it like this:

1. Clear the local Maven repository (~.m2/repository) just in case
2. Run "mvn clean install" under jena-text
3. Run "mvn clean install" under jena-spatial
4. Run "mvn clean package" under jena-fuseki1

The resulting Fuseki package under target/ should now contain the 
jena-text and jena-spatial modules built with Lucene 5.5.3.



I tried building jena-fuseki2 too, but it failed with an error that I 
suspect is not related to the Lucene changes.


Hope this helps,
Osma

06.01.2017, 14:27, Samur Araujo wrote:

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 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 so that the state of it is known.

https://github.com/jmvanel/jena/commits/master

is not the Jena projects code repository - as ajs6f says, you will have to
take this up with the maintainer of that fork, Jean-Marc Vanel (jmvanel)
and find out what the state of work there is.

Andy



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 ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 111 source files to
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
core/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.7:testResources
(default-testResources)
@ jena-fuseki-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
core/src/test/resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile)
@
jena-fuseki-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 19 source files to
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
core/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
jena-fuseki-core ---

---
 T E S T S
---
Running org.apache.jena.fuseki.TS_Fuseki
[2017-01-05 17:11:41] riot   ERROR [line: 6, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
Exception in thread "Thread-73" org.apache.jena.riot.RiotException:
[line:
6, col: 7 ] Unexpected attribute : :datatype at typedLiteral
at
org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandler
Std.error(ErrorHandlerFactory.java:128)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
at
org.apache.jena.riot.RDFDataMgr.lambda$createIteratorTriples
$0(RDFDataMgr.java:1250)
at java.lang.Thread.run(Thread.java:745)
[2017-01-05 17:11:51] riot   ERROR [line: 6, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
[2017-01-05 17:11:51] riot   ERROR [line: 7, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
Exception in thread "Thread-81" org.apache.jena.riot.RiotException:
[line:
7, col: 7 ] Unexpected attribute : :datatype at typedLiteral
at
org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandler
Std.error(ErrorHandlerFactory.java:128)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
at

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 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 so that the state of it is known.
>
> https://github.com/jmvanel/jena/commits/master
>
> is not the Jena projects code repository - as ajs6f says, you will have to
> take this up with the maintainer of that fork, Jean-Marc Vanel (jmvanel)
> and find out what the state of work there is.
>
> Andy
>
>
>> 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 ---
>> [INFO] Changes detected - recompiling the module!
>> [INFO] Compiling 111 source files to
>> /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
>> core/target/classes
>> [INFO]
>> [INFO] --- maven-resources-plugin:2.7:testResources
>> (default-testResources)
>> @ jena-fuseki-core ---
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] skip non existing resourceDirectory
>> /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
>> core/src/test/resources
>> [INFO] Copying 3 resources
>> [INFO]
>> [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile)
>> @
>> jena-fuseki-core ---
>> [INFO] Changes detected - recompiling the module!
>> [INFO] Compiling 19 source files to
>> /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-
>> core/target/test-classes
>> [INFO]
>> [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
>> jena-fuseki-core ---
>>
>> ---
>>  T E S T S
>> ---
>> Running org.apache.jena.fuseki.TS_Fuseki
>> [2017-01-05 17:11:41] riot   ERROR [line: 6, col: 7 ] Unexpected
>> attribute : :datatype at typedLiteral
>> Exception in thread "Thread-73" org.apache.jena.riot.RiotException:
>> [line:
>> 6, col: 7 ] Unexpected attribute : :datatype at typedLiteral
>> at
>> org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandler
>> Std.error(ErrorHandlerFactory.java:128)
>> at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
>> at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
>> at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
>> at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
>> at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
>> at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
>> at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
>> at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
>> at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
>> at
>> org.apache.jena.riot.RDFDataMgr.lambda$createIteratorTriples
>> $0(RDFDataMgr.java:1250)
>> at java.lang.Thread.run(Thread.java:745)
>> [2017-01-05 17:11:51] riot   ERROR [line: 6, col: 7 ] Unexpected
>> attribute : :datatype at typedLiteral
>> [2017-01-05 17:11:51] riot   ERROR [line: 7, col: 7 ] Unexpected
>> attribute : :datatype at typedLiteral
>> Exception in thread "Thread-81" org.apache.jena.riot.RiotException:
>> [line:
>> 7, col: 7 ] Unexpected attribute : :datatype at typedLiteral
>> at
>> org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandler
>> Std.error(ErrorHandlerFactory.java:128)
>> at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
>> at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
>> at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
>> at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
>> at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
>> at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
>> at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
>> at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
>> at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
>> at
>> org.apache.jena.riot.RDFDataMgr.lambda$createIteratorQuads$
>> 1(RDFDataMgr.java:1270)
>> at java.lang.Thread.run(Thread.java:745)
>> Tests run: 168, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 24.439
>> sec <<< FAILURE! - in org.apache.jena.fuseki.TS_Fuseki
>> query_construct_conneg(org.apache.jena.fuseki.TestQuery)  Time elapsed:
>> 10.084 sec  <<< ERROR!
>> org.apache.jena.riot.RiotException: Producer failed to ever call start(),
>> declaring producer dead
>> at
>> org.apache.jena.fuseki.TestQuery.query_construct_conneg(
>> TestQuery.java:217)
>>
>>

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 so that the state of 
it is known.


https://github.com/jmvanel/jena/commits/master

is not the Jena projects code repository - as ajs6f says, you will have 
to take this up with the maintainer of that fork, Jean-Marc Vanel 
(jmvanel) and find out what the state of work there is.


Andy



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 ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 111 source files to
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources)
@ jena-fuseki-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/src/test/resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @
jena-fuseki-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 19 source files to
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
jena-fuseki-core ---

---
 T E S T S
---
Running org.apache.jena.fuseki.TS_Fuseki
[2017-01-05 17:11:41] riot   ERROR [line: 6, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
Exception in thread "Thread-73" org.apache.jena.riot.RiotException: [line:
6, col: 7 ] Unexpected attribute : :datatype at typedLiteral
at
org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
at
org.apache.jena.riot.RDFDataMgr.lambda$createIteratorTriples$0(RDFDataMgr.java:1250)
at java.lang.Thread.run(Thread.java:745)
[2017-01-05 17:11:51] riot   ERROR [line: 6, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
[2017-01-05 17:11:51] riot   ERROR [line: 7, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
Exception in thread "Thread-81" org.apache.jena.riot.RiotException: [line:
7, col: 7 ] Unexpected attribute : :datatype at typedLiteral
at
org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
at
org.apache.jena.riot.RDFDataMgr.lambda$createIteratorQuads$1(RDFDataMgr.java:1270)
at java.lang.Thread.run(Thread.java:745)
Tests run: 168, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 24.439
sec <<< FAILURE! - in org.apache.jena.fuseki.TS_Fuseki
query_construct_conneg(org.apache.jena.fuseki.TestQuery)  Time elapsed:
10.084 sec  <<< ERROR!
org.apache.jena.riot.RiotException: Producer failed to ever call start(),
declaring producer dead
at
org.apache.jena.fuseki.TestQuery.query_construct_conneg(TestQuery.java:217)

query_describe_conneg(org.apache.jena.fuseki.TestQuery)  Time elapsed:
0.111 sec  <<< ERROR!
org.apache.jena.riot.RiotException: [line: 6, col: 7 ] Unexpected attribute
: :datatype at typedLiteral
at
org.apache.jena.fuseki.TestQuery.query_describe_conneg(TestQuery.java:251)

query_construct_quad_conneg(org.apache.jena.fuseki.TestQuery)  Time
elapsed: 10.263 sec  <<< ERROR!
org.apache.jena.riot.RiotException: Producer failed to ever call start(),
declaring producer dead
at

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] --- maven-compiler-plugin:3.5.1:compile (default-compile) @
> jena-fuseki-core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 111 source files to
> /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/target/classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:testResources (default-testResources)
> @ jena-fuseki-core ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/src/test/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @
> jena-fuseki-core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 19 source files to
> /home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
> jena-fuseki-core ---
>
> ---
>  T E S T S
> ---
> Running org.apache.jena.fuseki.TS_Fuseki
> [2017-01-05 17:11:41] riot   ERROR [line: 6, col: 7 ] Unexpected
> attribute : :datatype at typedLiteral
> Exception in thread "Thread-73" org.apache.jena.riot.RiotException: [line:
> 6, col: 7 ] Unexpected attribute : :datatype at typedLiteral
> at
> org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
> at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
> at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
> at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
> at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
> at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
> at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
> at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
> at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
> at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
> at
> org.apache.jena.riot.RDFDataMgr.lambda$createIteratorTriples$0(RDFDataMgr.java:1250)
> at java.lang.Thread.run(Thread.java:745)
> [2017-01-05 17:11:51] riot   ERROR [line: 6, col: 7 ] Unexpected
> attribute : :datatype at typedLiteral
> [2017-01-05 17:11:51] riot   ERROR [line: 7, col: 7 ] Unexpected
> attribute : :datatype at typedLiteral
> Exception in thread "Thread-81" org.apache.jena.riot.RiotException: [line:
> 7, col: 7 ] Unexpected attribute : :datatype at typedLiteral
> at
> org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
> at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
> at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
> at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
> at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
> at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
> at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
> at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
> at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
> at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
> at
> org.apache.jena.riot.RDFDataMgr.lambda$createIteratorQuads$1(RDFDataMgr.java:1270)
> at java.lang.Thread.run(Thread.java:745)
> Tests run: 168, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 24.439
> sec <<< FAILURE! - in org.apache.jena.fuseki.TS_Fuseki
> query_construct_conneg(org.apache.jena.fuseki.TestQuery)  Time elapsed:
> 10.084 sec  <<< ERROR!
> org.apache.jena.riot.RiotException: Producer failed to ever call start(),
> declaring producer dead
> at
> org.apache.jena.fuseki.TestQuery.query_construct_conneg(TestQuery.java:217)
>
> query_describe_conneg(org.apache.jena.fuseki.TestQuery)  Time elapsed:
> 0.111 sec  <<< ERROR!
> org.apache.jena.riot.RiotException: [line: 6, col: 7 ] Unexpected attribute
> : :datatype at typedLiteral
> at
> org.apache.jena.fuseki.TestQuery.query_describe_conneg(TestQuery.java:251)
>
> query_construct_quad_conneg(org.apache.jena.fuseki.TestQuery)  Time
> elapsed: 10.263 sec  <<< ERROR!
> org.apache.jena.riot.RiotException: Producer failed to ever call start(),
> declaring producer dead
> at
> org.apache.jena.fuseki.TestQuery.query_construct_quad_conneg(TestQuery.java:235)
>
>
> Results :
>
> Tests in error:
>   TestQuery.query_construct_conneg:217 » Riot Producer failed to ever call
> start...
>   TestQuery.query_construct_quad_conneg:235 » Riot Producer failed to ever
> call ...
>   TestQuery.query_describe_conneg:251 » Riot

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 ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 111 source files to
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources)
@ jena-fuseki-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/src/test/resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @
jena-fuseki-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 19 source files to
/home/samur/Downloads/jena-master/jena-fuseki2/jena-fuseki-core/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
jena-fuseki-core ---

---
 T E S T S
---
Running org.apache.jena.fuseki.TS_Fuseki
[2017-01-05 17:11:41] riot   ERROR [line: 6, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
Exception in thread "Thread-73" org.apache.jena.riot.RiotException: [line:
6, col: 7 ] Unexpected attribute : :datatype at typedLiteral
at
org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
at
org.apache.jena.riot.RDFDataMgr.lambda$createIteratorTriples$0(RDFDataMgr.java:1250)
at java.lang.Thread.run(Thread.java:745)
[2017-01-05 17:11:51] riot   ERROR [line: 6, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
[2017-01-05 17:11:51] riot   ERROR [line: 7, col: 7 ] Unexpected
attribute : :datatype at typedLiteral
Exception in thread "Thread-81" org.apache.jena.riot.RiotException: [line:
7, col: 7 ] Unexpected attribute : :datatype at typedLiteral
at
org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:419)
at org.apache.jena.riot.lang.ReaderTriX.staxError(ReaderTriX.java:415)
at org.apache.jena.riot.lang.ReaderTriX.attribute(ReaderTriX.java:404)
at org.apache.jena.riot.lang.ReaderTriX.term(ReaderTriX.java:288)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:215)
at org.apache.jena.riot.lang.ReaderTriX.read(ReaderTriX.java:85)
at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:859)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:698)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:687)
at
org.apache.jena.riot.RDFDataMgr.lambda$createIteratorQuads$1(RDFDataMgr.java:1270)
at java.lang.Thread.run(Thread.java:745)
Tests run: 168, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 24.439
sec <<< FAILURE! - in org.apache.jena.fuseki.TS_Fuseki
query_construct_conneg(org.apache.jena.fuseki.TestQuery)  Time elapsed:
10.084 sec  <<< ERROR!
org.apache.jena.riot.RiotException: Producer failed to ever call start(),
declaring producer dead
at
org.apache.jena.fuseki.TestQuery.query_construct_conneg(TestQuery.java:217)

query_describe_conneg(org.apache.jena.fuseki.TestQuery)  Time elapsed:
0.111 sec  <<< ERROR!
org.apache.jena.riot.RiotException: [line: 6, col: 7 ] Unexpected attribute
: :datatype at typedLiteral
at
org.apache.jena.fuseki.TestQuery.query_describe_conneg(TestQuery.java:251)

query_construct_quad_conneg(org.apache.jena.fuseki.TestQuery)  Time
elapsed: 10.263 sec  <<< ERROR!
org.apache.jena.riot.RiotException: Producer failed to ever call start(),
declaring producer dead
at
org.apache.jena.fuseki.TestQuery.query_construct_quad_conneg(TestQuery.java:235)


Results :

Tests in error:
  TestQuery.query_construct_conneg:217 » Riot Producer failed to ever call
start...
  TestQuery.query_construct_quad_conneg:235 » Riot Producer failed to ever
call ...
  TestQuery.query_describe_conneg:251 » Riot [line: 6, col: 7 ] Unexpected
attri...

Tests run: 168, Failures: 0, Errors: 3, Skipped: 0

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Apache Jena - Parent

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
org.apache.jena.riot.tokens.TestTokenizer.tokenFirst(TestTokenizer.java:45)
at
org.apache.jena.riot.tokens.TestTokenizer.tokenUnit_iri18(TestTokenizer.java:205)



The code you are compiling is behind the Apache codebase.

It looks like it could be this:

https://github.com/apache/jena/commit/0cc1d1a01f0e9ce1656d48ad5b93095b6cdea263

Andy

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 point, or 
perhaps the issue:

https://issues.apache.org/jira/browse/JENA-1250

---
A. Soroka
The University of Virginia Library

> On Jan 5, 2017, at 10:26 AM, Samur Araujo  wrote:
> 
> 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 org.apache.jena.system.TS_System
> Tests run: 51, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.054 sec
> - in org.apache.jena.system.TS_System
> Running org.apache.jena.common.TS_Common
> Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.104 sec
> - in org.apache.jena.common.TS_Common
> Running org.apache.jena.query.TS_ParamString
> Tests run: 140, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.262 sec
> - in org.apache.jena.query.TS_ParamString
> Running org.apache.jena.riot.out.TS_Out
> Tests run: 128, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec
> - in org.apache.jena.riot.out.TS_Out
> Running org.apache.jena.riot.web.TS_RiotWeb
> Tests run: 39, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> - in org.apache.jena.riot.web.TS_RiotWeb
> Running org.apache.jena.riot.tokens.TS_Tokens
> Tests run: 144, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.039 sec
> <<< 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
> org.apache.jena.riot.tokens.TestTokenizer.tokenFirst(TestTokenizer.java:45)
> at
> org.apache.jena.riot.tokens.TestTokenizer.tokenUnit_iri18(TestTokenizer.java:205)
> 
> Running org.apache.jena.riot.system.TS_RiotSystem
> Tests run: 296, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.444 sec
> - in org.apache.jena.riot.system.TS_RiotSystem
> Running org.apache.jena.riot.resultset.TS_ResultSetRIOT
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.052 sec -
> in org.apache.jena.riot.resultset.TS_ResultSetRIOT
> Running org.apache.jena.riot.writer.TS_RiotWriter
> Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.16 sec
> - in org.apache.jena.riot.writer.TS_RiotWriter
> Running org.apache.jena.riot.thrift.TS_RDFThrift
> Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
> - in org.apache.jena.riot.thrift.TS_RDFThrift
> Running org.apache.jena.riot.TS_RiotGeneral
> Tests run: 122, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.066 sec
> - in org.apache.jena.riot.TS_RiotGeneral
> Running org.apache.jena.riot.stream.TS_IO2
> Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec
> - in org.apache.jena.riot.stream.TS_IO2
> Running org.apache.jena.riot.lang.TS_Lang
> Tests run: 458, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.736 sec
> - in org.apache.jena.riot.lang.TS_Lang
> Running org.apache.jena.riot.adapters.TS_RIOTAdapters
> Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
> - in org.apache.jena.riot.adapters.TS_RIOTAdapters
> Running org.apache.jena.riot.TS_LangSuite
> Tests run: 861, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.502 sec
> - in org.apache.jena.riot.TS_LangSuite
> Running org.apache.jena.riot.process.TS_Process
> Tests run: 60, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec
> - in org.apache.jena.riot.process.TS_Process
> Running org.apache.jena.atlas.web.TS_Web
> Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> - in org.apache.jena.atlas.web.TS_Web
> Running org.apache.jena.atlas.json.TS_JSON
> Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec -
> in org.apache.jena.atlas.json.TS_JSON
> Running org.apache.jena.atlas.event.TS_Event
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec -
> in org.apache.jena.atlas.event.TS_Event
> Running org.apache.jena.atlas.data.TS_Data
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.603 sec
> - in org.apache.jena.atlas.data.TS_Data
> Running org.apache.jena.sparql.TC_DAWG
> Tests run: 467, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.867 sec
> - in org.apache.jena.sparql.TC_DAWG
> Running org.apache.jena.sparql.resultset.TS_ResultSet
> Tests run: 136, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec
> - in org.apache.jena.sparql.resultset.TS_ResultSet
> Running org.apache.jena.sparql.core.assembler.TS_Assembler
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0,

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 org.apache.jena.system.TS_System
Tests run: 51, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.054 sec
- in org.apache.jena.system.TS_System
Running org.apache.jena.common.TS_Common
Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.104 sec
- in org.apache.jena.common.TS_Common
Running org.apache.jena.query.TS_ParamString
Tests run: 140, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.262 sec
- in org.apache.jena.query.TS_ParamString
Running org.apache.jena.riot.out.TS_Out
Tests run: 128, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec
- in org.apache.jena.riot.out.TS_Out
Running org.apache.jena.riot.web.TS_RiotWeb
Tests run: 39, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
- in org.apache.jena.riot.web.TS_RiotWeb
Running org.apache.jena.riot.tokens.TS_Tokens
Tests run: 144, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.039 sec
<<< 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
org.apache.jena.riot.tokens.TestTokenizer.tokenFirst(TestTokenizer.java:45)
at
org.apache.jena.riot.tokens.TestTokenizer.tokenUnit_iri18(TestTokenizer.java:205)

Running org.apache.jena.riot.system.TS_RiotSystem
Tests run: 296, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.444 sec
- in org.apache.jena.riot.system.TS_RiotSystem
Running org.apache.jena.riot.resultset.TS_ResultSetRIOT
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.052 sec -
in org.apache.jena.riot.resultset.TS_ResultSetRIOT
Running org.apache.jena.riot.writer.TS_RiotWriter
Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.16 sec
- in org.apache.jena.riot.writer.TS_RiotWriter
Running org.apache.jena.riot.thrift.TS_RDFThrift
Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
- in org.apache.jena.riot.thrift.TS_RDFThrift
Running org.apache.jena.riot.TS_RiotGeneral
Tests run: 122, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.066 sec
- in org.apache.jena.riot.TS_RiotGeneral
Running org.apache.jena.riot.stream.TS_IO2
Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec
- in org.apache.jena.riot.stream.TS_IO2
Running org.apache.jena.riot.lang.TS_Lang
Tests run: 458, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.736 sec
- in org.apache.jena.riot.lang.TS_Lang
Running org.apache.jena.riot.adapters.TS_RIOTAdapters
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
- in org.apache.jena.riot.adapters.TS_RIOTAdapters
Running org.apache.jena.riot.TS_LangSuite
Tests run: 861, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.502 sec
- in org.apache.jena.riot.TS_LangSuite
Running org.apache.jena.riot.process.TS_Process
Tests run: 60, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec
- in org.apache.jena.riot.process.TS_Process
Running org.apache.jena.atlas.web.TS_Web
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
- in org.apache.jena.atlas.web.TS_Web
Running org.apache.jena.atlas.json.TS_JSON
Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec -
in org.apache.jena.atlas.json.TS_JSON
Running org.apache.jena.atlas.event.TS_Event
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec -
in org.apache.jena.atlas.event.TS_Event
Running org.apache.jena.atlas.data.TS_Data
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.603 sec
- in org.apache.jena.atlas.data.TS_Data
Running org.apache.jena.sparql.TC_DAWG
Tests run: 467, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.867 sec
- in org.apache.jena.sparql.TC_DAWG
Running org.apache.jena.sparql.resultset.TS_ResultSet
Tests run: 136, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec
- in org.apache.jena.sparql.resultset.TS_ResultSet
Running org.apache.jena.sparql.core.assembler.TS_Assembler
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec -
in org.apache.jena.sparql.core.assembler.TS_Assembler
Running org.apache.jena.sparql.core.TS_Core
Tests run: 245, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.099 sec
- in org.apache.jena.sparql.core.TS_Core
Running org.apache.jena.sparql.core.mem.TS_DatasetTxnMem
Tests run: 142, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.031 sec
- in org.apache.jena.sparql.core.mem.TS_DatasetTxnMem
Running org.apache.jena.sparql.syntax.TS_Syntax
Tests run: 89, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.117 sec
- in org.apache.jena.sparql.syntax.TS_Syntax
Running org.apache.jena.sparql.syntax.TS_SSE
Tests run: 127, Failures: 0,

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, Samur Araujo  wrote:
> 
> 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 at 16:05, A. Soroka  wrote:
> 
>> 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
>> compile a mix of modules? Are you trying to maintain both ordinary and
>> forked forms of Jena in your local Maven repo? What do you intend to do
>> with the forked artifacts? Are you going to integrate them into some other
>> application? There may be an easier way to do all this.
>> 
>> ---
>> A. Soroka
>> The University of Virginia Library
>> 
>>> On Jan 5, 2017, at 10:01 AM, Samur Araujo  wrote:
>>> 
>>> 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 Apache Jena - Fuseki Server Engine 3.1.1-myfork-SNAPSHOT
>>> [INFO]
>>> 
>>> [WARNING] The POM for org.apache.jena:jena-text:jar:
>> 3.1.1-myfork-SNAPSHOT
>>> is missing, no dependency information available
>>> [WARNING] The POM for
>>> org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT is missing, no
>>> dependency information available
>>> [INFO]
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache Jena - Parent ... SUCCESS [
>>> 1.552 s]
>>> [INFO] Apache Jena - Base Common Environment .. SUCCESS [
>>> 8.325 s]
>>> [INFO] Apache Jena - Core . SUCCESS [
>>> 11.643 s]
>>> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine)  SUCCESS [
>>> 19.718 s]
>>> [INFO] Apache Jena - TDB (Native Triple Store)  SUCCESS [
>>> 2.547 s]
>>> [INFO] Apache Jena - Libraries POM  SUCCESS [
>>> 0.234 s]
>>> [INFO] Apache Jena - Command line tools ... SUCCESS [
>>> 5.790 s]
>>> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server . SUCCESS [
>>> 0.047 s]
>>> [INFO] Apache Jena - Fuseki Server Engine . FAILURE [
>>> 0.045 s]
>>> [INFO] Apache Jena - Fuseki Embedded Server ... SKIPPED
>>> [INFO] Apache Jena - Fuseki WAR File .. SKIPPED
>>> [INFO] Apache Jena - Fuseki Server Standalone Jar . SKIPPED
>>> [INFO] Apache Jena - Fuseki Binary Distribution ... SKIPPED
>>> [INFO] Apache Jena - Security Permissions . SKIPPED
>>> [INFO] Apache Jena  SKIPPED
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 50.588 s
>>> [INFO] Finished at: 2017-01-05T15:56:51+01:00
>>> [INFO] Final Memory: 60M/1801M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal on project jena-fuseki-core: Could not
>>> resolve dependencies for project
>>> org.apache.jena:jena-fuseki-core:jar:3.1.1-myfork-SNAPSHOT: The
>> following
>>> artifacts could not be resolved:
>>> org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT,
>>> org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT: Failure to find
>>> org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT in
>>> http://repository.apache.org/snapshots was cached in the local
>> repository,
>>> resolution will not be reattempted until the update interval of
>>> apache.snapshots has elapsed or updates are forced -> [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/
>>

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 at 16:05, A. Soroka  wrote:

> 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
> compile a mix of modules? Are you trying to maintain both ordinary and
> forked forms of Jena in your local Maven repo? What do you intend to do
> with the forked artifacts? Are you going to integrate them into some other
> application? There may be an easier way to do all this.
>
> ---
> A. Soroka
> The University of Virginia Library
>
> > On Jan 5, 2017, at 10:01 AM, Samur Araujo  wrote:
> >
> > 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 Apache Jena - Fuseki Server Engine 3.1.1-myfork-SNAPSHOT
> > [INFO]
> > 
> > [WARNING] The POM for org.apache.jena:jena-text:jar:
> 3.1.1-myfork-SNAPSHOT
> > is missing, no dependency information available
> > [WARNING] The POM for
> > org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT is missing, no
> > dependency information available
> > [INFO]
> > 
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache Jena - Parent ... SUCCESS [
> > 1.552 s]
> > [INFO] Apache Jena - Base Common Environment .. SUCCESS [
> > 8.325 s]
> > [INFO] Apache Jena - Core . SUCCESS [
> > 11.643 s]
> > [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine)  SUCCESS [
> > 19.718 s]
> > [INFO] Apache Jena - TDB (Native Triple Store)  SUCCESS [
> > 2.547 s]
> > [INFO] Apache Jena - Libraries POM  SUCCESS [
> > 0.234 s]
> > [INFO] Apache Jena - Command line tools ... SUCCESS [
> > 5.790 s]
> > [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server . SUCCESS [
> > 0.047 s]
> > [INFO] Apache Jena - Fuseki Server Engine . FAILURE [
> > 0.045 s]
> > [INFO] Apache Jena - Fuseki Embedded Server ... SKIPPED
> > [INFO] Apache Jena - Fuseki WAR File .. SKIPPED
> > [INFO] Apache Jena - Fuseki Server Standalone Jar . SKIPPED
> > [INFO] Apache Jena - Fuseki Binary Distribution ... SKIPPED
> > [INFO] Apache Jena - Security Permissions . SKIPPED
> > [INFO] Apache Jena  SKIPPED
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Total time: 50.588 s
> > [INFO] Finished at: 2017-01-05T15:56:51+01:00
> > [INFO] Final Memory: 60M/1801M
> > [INFO]
> > 
> > [ERROR] Failed to execute goal on project jena-fuseki-core: Could not
> > resolve dependencies for project
> > org.apache.jena:jena-fuseki-core:jar:3.1.1-myfork-SNAPSHOT: The
> following
> > artifacts could not be resolved:
> > org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT,
> > org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT: Failure to find
> > org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT in
> > http://repository.apache.org/snapshots was cached in the local
> repository,
> > resolution will not be reattempted until the update interval of
> > apache.snapshots has elapsed or updates are forced -> [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/
> DependencyResolutionException
> > [ERROR]
> > [ERROR] After correcting the problems, you can resume the build with the
> > command
> > [ERROR]   mvn  -rf :jena-fuseki-core
> >
> >
> > Notice the jena spatial and text are there:
> >
> > ~/tools/jena-master-forked$ find . | grep text | grep jar
> > ./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT-javadoc.jar
> >

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 compile a 
mix of modules? Are you trying to maintain both ordinary and forked forms of 
Jena in your local Maven repo? What do you intend to do with the forked 
artifacts? Are you going to integrate them into some other application? There 
may be an easier way to do all this.

---
A. Soroka
The University of Virginia Library

> On Jan 5, 2017, at 10:01 AM, Samur Araujo  wrote:
> 
> 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 Apache Jena - Fuseki Server Engine 3.1.1-myfork-SNAPSHOT
> [INFO]
> 
> [WARNING] The POM for org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT
> is missing, no dependency information available
> [WARNING] The POM for
> org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT is missing, no
> dependency information available
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Jena - Parent ... SUCCESS [
> 1.552 s]
> [INFO] Apache Jena - Base Common Environment .. SUCCESS [
> 8.325 s]
> [INFO] Apache Jena - Core . SUCCESS [
> 11.643 s]
> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine)  SUCCESS [
> 19.718 s]
> [INFO] Apache Jena - TDB (Native Triple Store)  SUCCESS [
> 2.547 s]
> [INFO] Apache Jena - Libraries POM  SUCCESS [
> 0.234 s]
> [INFO] Apache Jena - Command line tools ... SUCCESS [
> 5.790 s]
> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server . SUCCESS [
> 0.047 s]
> [INFO] Apache Jena - Fuseki Server Engine . FAILURE [
> 0.045 s]
> [INFO] Apache Jena - Fuseki Embedded Server ... SKIPPED
> [INFO] Apache Jena - Fuseki WAR File .. SKIPPED
> [INFO] Apache Jena - Fuseki Server Standalone Jar . SKIPPED
> [INFO] Apache Jena - Fuseki Binary Distribution ... SKIPPED
> [INFO] Apache Jena - Security Permissions . SKIPPED
> [INFO] Apache Jena  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 50.588 s
> [INFO] Finished at: 2017-01-05T15:56:51+01:00
> [INFO] Final Memory: 60M/1801M
> [INFO]
> 
> [ERROR] Failed to execute goal on project jena-fuseki-core: Could not
> resolve dependencies for project
> org.apache.jena:jena-fuseki-core:jar:3.1.1-myfork-SNAPSHOT: The following
> artifacts could not be resolved:
> org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT,
> org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT: Failure to find
> org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT in
> http://repository.apache.org/snapshots was cached in the local repository,
> resolution will not be reattempted until the update interval of
> apache.snapshots has elapsed or updates are forced -> [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/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :jena-fuseki-core
> 
> 
> Notice the jena spatial and text are there:
> 
> ~/tools/jena-master-forked$ find . | grep text | grep jar
> ./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT-javadoc.jar
> ./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT-sources.jar
> ./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT.jar
> 
> 
> ~/tools/jena-master-forked$ find . | grep spatial | grep jar
> ./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT.jar
> ./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT-sources.jar
> ./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT-javadoc.jar
> 
> 
> Am I missing anything else?
> 
> The fork I am trying to compile is this one:
> 
> https://github.com/jmvanel/jena/commits/master
> 
> 
> 
> On 5 January 2017 at 11:23, Andy Seaborne

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 Apache Jena - Fuseki Server Engine 3.1.1-myfork-SNAPSHOT
[INFO]

[WARNING] The POM for org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT
is missing, no dependency information available
[WARNING] The POM for
org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Apache Jena - Parent ... SUCCESS [
 1.552 s]
[INFO] Apache Jena - Base Common Environment .. SUCCESS [
 8.325 s]
[INFO] Apache Jena - Core . SUCCESS [
11.643 s]
[INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine)  SUCCESS [
19.718 s]
[INFO] Apache Jena - TDB (Native Triple Store)  SUCCESS [
 2.547 s]
[INFO] Apache Jena - Libraries POM  SUCCESS [
 0.234 s]
[INFO] Apache Jena - Command line tools ... SUCCESS [
 5.790 s]
[INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server . SUCCESS [
 0.047 s]
[INFO] Apache Jena - Fuseki Server Engine . FAILURE [
 0.045 s]
[INFO] Apache Jena - Fuseki Embedded Server ... SKIPPED
[INFO] Apache Jena - Fuseki WAR File .. SKIPPED
[INFO] Apache Jena - Fuseki Server Standalone Jar . SKIPPED
[INFO] Apache Jena - Fuseki Binary Distribution ... SKIPPED
[INFO] Apache Jena - Security Permissions . SKIPPED
[INFO] Apache Jena  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 50.588 s
[INFO] Finished at: 2017-01-05T15:56:51+01:00
[INFO] Final Memory: 60M/1801M
[INFO]

[ERROR] Failed to execute goal on project jena-fuseki-core: Could not
resolve dependencies for project
org.apache.jena:jena-fuseki-core:jar:3.1.1-myfork-SNAPSHOT: The following
artifacts could not be resolved:
org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT: Failure to find
org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT in
http://repository.apache.org/snapshots was cached in the local repository,
resolution will not be reattempted until the update interval of
apache.snapshots has elapsed or updates are forced -> [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/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :jena-fuseki-core

Notice the jena spatial and text are there:

~/tools/jena-master-forked$ find . | grep text | grep jar
./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT-javadoc.jar
./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT-sources.jar
./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT.jar

~/tools/jena-master-forked$ find . | grep spatial | grep jar
./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT.jar
./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT-sources.jar
./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT-javadoc.jar

Am I missing anything else?

The fork I am trying to compile is this one:

https://github.com/jmvanel/jena/commits/master

On 5 January 2017 at 11:23, Andy Seaborne  wrote:

>
>
> 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"  wrote:
>>
>> 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
>>
>
> Why not run mvn at the top level?
>
> mvn clean install
>
> or (quicker but not all of Jena):
>
> mvn clean
> mvn install -Pbootstrap
> mvn install -Pdev
>
> these profiles are documented in the POM - you seem to have changed
> the version everywhere so you may need -Pbootstrap
>
> otherwise -Pdev is a fast build(and

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"  wrote:

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


Why not run mvn at the top level?

mvn clean install

or (quicker but not all of Jena):

mvn clean
mvn install -Pbootstrap
mvn install -Pdev

these profiles are documented in the POM - you seem to have changed
the version everywhere so you may need -Pbootstrap

otherwise -Pdev is a fast build(and test!) of modules up to Fuseki2



[INFO] Scanning for projects...
[INFO]

[INFO]

[INFO] Building Apache Jena - ARQ (SPARQL 1.1 Query Engine)
3.1.1-myfork-SNAPSHOT
[INFO]

Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for org.apache.jena:jena-core:jar:3.1.1-myfork-SNAPSHOT
is missing, no dependency information available
[WARNING] The POM for
org.apache.jena:jena-core:jar:tests:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/jena-base-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for
org.apache.jena:jena-base:jar:tests:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/jena-shaded-guava-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for
org.apache.jena:jena-shaded-guava:jar:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT.jar
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT-tests.jar
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/jena-base-3.1.1-myfork-SNAPSHOT-tests.jar
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/jena-shaded-guava-3.1.1-myfork-SNAPSHOT.jar
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 3.449 s
[INFO] Finished at: 2017-01-05T08:42:05+01:00
[INFO] Final Memory: 19M/480M
[INFO]

[ERROR] Failed to execute goal on project jena-arq: Could not resolve
dependencies for project
org.apache.jena:jena-arq:jar:3.1.1-myfork-SNAPSHOT: The following artifacts
could not be resolved: org.apache.jena:jena-core:jar:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-core:jar:tests:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-base:jar:tests:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-shaded-guava:jar:3.1.1-myfork-SNAPSHOT: Could not find
artifact org.apache.jena:jena

On 4 January 2017 at 17:58, Rob Vesse  wrote:

> 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 so:
>
> mvn release:update-versions -DdevelopmentVersion=3.1.1-myfork-SNAPSHOT
>
> Rob
>
> On 04/01/2017 16:23, "Andy Seaborne"  wrote:
>
> 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
> >
> >

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 missing any parameter?

~/tools/jena-master-forked/jena-arq$ mvn package
[INFO] Scanning for projects...
[INFO]

[INFO]

[INFO] Building Apache Jena - ARQ (SPARQL 1.1 Query Engine)
3.1.1-myfork-SNAPSHOT
[INFO]

Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for org.apache.jena:jena-core:jar:3.1.1-myfork-SNAPSHOT
is missing, no dependency information available
[WARNING] The POM for
org.apache.jena:jena-core:jar:tests:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/jena-base-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for
org.apache.jena:jena-base:jar:tests:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/jena-shaded-guava-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for
org.apache.jena:jena-shaded-guava:jar:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT.jar
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT-tests.jar
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/jena-base-3.1.1-myfork-SNAPSHOT-tests.jar
Downloading:

http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/jena-shaded-guava-3.1.1-myfork-SNAPSHOT.jar
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 3.449 s
[INFO] Finished at: 2017-01-05T08:42:05+01:00
[INFO] Final Memory: 19M/480M
[INFO]

[ERROR] Failed to execute goal on project jena-arq: Could not resolve
dependencies for project
org.apache.jena:jena-arq:jar:3.1.1-myfork-SNAPSHOT: The following artifacts
could not be resolved: org.apache.jena:jena-core:jar:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-core:jar:tests:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-base:jar:tests:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-shaded-guava:jar:3.1.1-myfork-SNAPSHOT: Could not find
artifact org.apache.jena:jena

On 4 January 2017 at 17:58, Rob Vesse  wrote:

> 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 so:
>
> mvn release:update-versions -DdevelopmentVersion=3.1.1-myfork-SNAPSHOT
>
> Rob
>
> On 04/01/2017 16:23, "Andy Seaborne"  wrote:
>
> 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 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 it locally, in the
> jena-master local
> >> folder structure.
> >>
> >> Is there any

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]

[INFO] Building Apache Jena - ARQ (SPARQL 1.1 Query Engine)
3.1.1-myfork-SNAPSHOT
[INFO]

Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for org.apache.jena:jena-core:jar:3.1.1-myfork-SNAPSHOT
is missing, no dependency information available
[WARNING] The POM for
org.apache.jena:jena-core:jar:tests:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/jena-base-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for
org.apache.jena:jena-base:jar:tests:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/jena-shaded-guava-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for
org.apache.jena:jena-shaded-guava:jar:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT.jar
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT-tests.jar
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/jena-base-3.1.1-myfork-SNAPSHOT-tests.jar
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/jena-shaded-guava-3.1.1-myfork-SNAPSHOT.jar
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 3.449 s
[INFO] Finished at: 2017-01-05T08:42:05+01:00
[INFO] Final Memory: 19M/480M
[INFO]

[ERROR] Failed to execute goal on project jena-arq: Could not resolve
dependencies for project
org.apache.jena:jena-arq:jar:3.1.1-myfork-SNAPSHOT: The following artifacts
could not be resolved: org.apache.jena:jena-core:jar:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-core:jar:tests:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-base:jar:tests:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-shaded-guava:jar:3.1.1-myfork-SNAPSHOT: Could not find
artifact org.apache.jena:jena

On 4 January 2017 at 17:58, Rob Vesse  wrote:

> 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 so:
>
> mvn release:update-versions -DdevelopmentVersion=3.1.1-myfork-SNAPSHOT
>
> Rob
>
> On 04/01/2017 16:23, "Andy Seaborne"  wrote:
>
> 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 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 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 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 least once.
>

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 so:

mvn release:update-versions -DdevelopmentVersion=3.1.1-myfork-SNAPSHOT

Rob

On 04/01/2017 16:23, "Andy Seaborne"  wrote:

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 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 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 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 least once.
>>>
>>> See "mvn dependency:tree" (when online).
>>>
>>>

>>
>

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 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 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 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 least once.

See "mvn dependency:tree" (when online).

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 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 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 least once.
>>
>> See "mvn dependency:tree" (when online).
>>
>>
>>>
>

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 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 least once.
>
> See "mvn dependency:tree" (when online).
>
>
>>
>>


-- 
Senior Data Scientist
Geophy
www.geophy.com

Nieuwe Plantage 54-55
2611XK  Delft
+31 (0)70 7640725

1 Fore Street
EC2Y 9DT  London
+44 (0)20 37690760

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 least once.

See "mvn dependency:tree" (when online).

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

Re: Compile Forked Version

21 matches

Site Navigation

Mail list logo

Footer information