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

Andy Seaborne commented on JENA-2059:
-------------------------------------

The function exists: 
[IRIs.scheme|https://github.com/apache/jena/blob/66bf616bb276a06c614081e087f0ae92318eb27a/jena-core/src/main/java/org/apache/jena/irix/IRIs.java#L160].
 It went into main yesterday.

It looks like there is a mix of versions somewhere. With SNAPSHOTs, this is 
easy because a build may fetch "latest" and update automatically. Failuire to 
download one also can cause problems as then there is an inconsistent mix.

{{GraphFactory}} is in jena-arq although I guess this is first Jena code 
touched and it is system initialization happening. IRIs in jena-core. i.e. 
{{jena-arq}} and {{jena-core}} are snapshots and at run time, it's a mix.

Application code can cause initialization earlier if it wants, by adding 
{{JenaSystem.init()}} e.g in class initialization with {{ static { 
JenaSystem.init(); } }}.

Current: jena-core-4.0.0-20210301.214349-15


> 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