[ 
https://issues.apache.org/jira/browse/JENA-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293601#comment-17293601
 ] 

Florian Kleedorfer commented on JENA-2059:
------------------------------------------

We are seeing this consistently across different machines, on different 
networks and OSes. 

I deleted all my jena dependencies in the m2 repo and built again - same 
result. I repeatedly ran builds on our jenkins server, which downloads the 
latest jena jars each time - all fail in the same way. Last night ([01.03.2021 
21:14 |http://satvm03.researchstudio.at:8080/job/webofneeds-master/1871/]UTC+1) 
was the last successful build we had, no commits have been added since then.

It does not look like a mixed-dependency problem to me, or at least I am not 
seeing how.

For now we are pinning 4.0.0-20210225.080032-13, which works for us.

(For reference, this happens about 30 seconds into the {{mvn test}} build of 
[webofneeds|https://github.com/researchstudio-sat/webofneeds.git])

> GraphFactory.createGraphMem() fails
> -----------------------------------
>
>                 Key: JENA-2059
>                 URL: https://issues.apache.org/jira/browse/JENA-2059
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: ARQ
>    Affects Versions: Jena 4.0.0
>            Reporter: Florian Kleedorfer
>            Priority: Major
>
> Getting this with snapshot-version 4.0.0-20210301.214547-15:
> {noformat}
> java.lang.NoSuchMethodError: 'java.lang.String 
> org.apache.jena.irix.IRIs.scheme(java.lang.String)'
>         at ShaclCheckTest.loadGraph(ShaclCheckTest.java:99)
>         at ShaclCheckTest.loadGraph(ShaclCheckTest.java:107)
>         at ShaclCheckTest.loadShapes(ShaclCheckTest.java:88)
>         at ShaclCheckTest.loadAuthShapes(ShaclCheckTest.java:35)
> {noformat}
> The culprit at that line is:
> {noformat}
> Graph graph = GraphFactory.createGraphMem();
> {noformat}
> I could not find any hint that this is a planned change, so I am guessing 
> it's an unwanted sideeffect of the IRI refactoring.
> Version 4.0.0-20210225.075305
> -13 does not have this problem
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to