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

ASF GitHub Bot commented on ANY23-352:
--------------------------------------

GitHub user HansBrende opened a pull request:

    https://github.com/apache/any23/pull/83

    ANY23-352 updated to rdf4j version 2.3.2

    mvn clean test -> all tests pass
    
    @lewismc @JulioCCBUcuenca rdf4j version 2.3.2 defaults to pretty printing 
in the JSONLDWriter, so this PR seems to complement ANY23-231 nicely. Does that 
work for you?

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/HansBrende/any23 ANY23-352

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/any23/pull/83.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #83
    
----
commit e89c395949649a214df8364b412da190ff13c754
Author: Hans <firedrake93@...>
Date:   2018-05-16T04:02:38Z

    Added jsonld-java dependency to core, cli modules

commit e9aaeb03040581bce1ed5b63e4e57b670bf26dc0
Author: Hans <firedrake93@...>
Date:   2018-05-16T04:32:04Z

    ANY23-352 updated to rdf4j version 2.3.2

----


> Update to rdf4j version 2.3.2
> -----------------------------
>
>                 Key: ANY23-352
>                 URL: https://issues.apache.org/jira/browse/ANY23-352
>             Project: Apache Any23
>          Issue Type: Improvement
>          Components: extractors
>            Reporter: Hans Brende
>            Assignee: Hans Brende
>            Priority: Major
>             Fix For: 2.3
>
>
> We previously upgraded to rdf4j version 2.3.0/2.3.1 in ANY23-323, then we had 
> to roll back to version 2.2.4 in ANY23-346 due to a critical regression in 
> IRI parsing. That issue has since been fixed in version 2.3.2. See: 
> https://github.com/eclipse/rdf4j/releases/tag/2.3.2
> So now we should be able to upgrade to 2.3.2 without a problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to