GitHub user kinow opened a pull request:

    https://github.com/apache/jena/pull/177

    Bump YASQE up to version 2.11.3

    This should fix JENA-1072. Tested locally.
    
    
![screenshot_2016-10-10_20-38-20](https://cloud.githubusercontent.com/assets/304786/19229556/f141b5ca-8f2a-11e6-8de3-867e0e12e726.png)
    
    Basically executed:
    
    ```
    wget https://github.com/OpenTriply/YASGUI.YASQE/archive/v2.11.3.zip
    unzip v2.11.3.zip -d yasqe-2.11.3
    cd yasqe-2.11.3/
    
    cp YASGUI.YASQE-2.11.3/dist/yasqe.min.js 
~/Development/java/jena/jena/jena-fuseki2/jena-fuseki-core/src/main/webapp/js/lib/
    cp YASGUI.YASQE-2.11.3/dist/yasqe.min.js.map 
~/Development/java/jena/jena/jena-fuseki2/jena-fuseki-core/src/main/webapp/js/lib/
    cp YASGUI.YASQE-2.11.3/dist/yasqe.min.css 
~/Development/java/jena/jena/jena-fuseki2/jena-fuseki-core/src/main/webapp/css/
    ```
    
    YASQE 2.11.3 was released with the fix for the issue in the SPARQL syntax, 
after merging the pull request 
https://github.com/OpenTriply/YASGUI.YASQE/pull/89
    
    Sending as a pull request since this updates a library, and could introduce 
regressions. So in case anyone else would like to test it first, before it is 
merged and included in the next release, now is the time :-)
    
    Cheers
    Bruno

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

    $ git pull https://github.com/kinow/jena fix-JENA-1072

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

    https://github.com/apache/jena/pull/177.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 #177
    
----
commit 339d816814885befc91d73ea17a3a6cdd6d2dd7a
Author: Bruno P. Kinoshita <[email protected]>
Date:   2016-10-10T07:47:28Z

    Bump YASQE up to version 2.11.3

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to