You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by kinow <gi...@git.apache.org> on 2016/10/10 07:50:38 UTC

[GitHub] jena pull request #177: Bump YASQE up to version 2.11.3

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 <br...@yahoo.com.br>
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena issue #177: Bump YASQE up to version 2.11.4

Posted by afs <gi...@git.apache.org>.
Github user afs commented on the issue:

    https://github.com/apache/jena/pull/177
  
    Go for it!


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena issue #177: Bump YASQE up to version 2.11.4

Posted by kinow <gi...@git.apache.org>.
Github user kinow commented on the issue:

    https://github.com/apache/jena/pull/177
  
    I think so. Tested locally, validation looks good, performance as well. Haven't had any issues, and the query from JENA-1072 is marked as valid too. If we merge now it might be easier to get other people to play with Fuseki and confirm everything is OK too, before the next release.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena issue #177: Bump YASQE up to version 2.11.4

Posted by afs <gi...@git.apache.org>.
Github user afs commented on the issue:

    https://github.com/apache/jena/pull/177
  
    Phew!
    
    Is this ready to merge? From my side, sooner is better as we head towards a release.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena issue #177: Bump YASQE up to version 2.11.4

Posted by kinow <gi...@git.apache.org>.
Github user kinow commented on the issue:

    https://github.com/apache/jena/pull/177
  
    Added a new commit, and edited my comments and title. Now instead of 2.11.3 it is 2.11.4. @LaurensRietveld warned me about a regression in 2.11.3 (big thanks!). 2.11.4 includes the fix to our issue, plus the fix to the regression.
    
    FWIW, looks like the regression in 2.11.3 involved an infinite loop crash in the browser.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena pull request #177: Bump YASQE up to version 2.11.4

Posted by kinow <gi...@git.apache.org>.
Github user kinow closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena issue #177: Bump YASQE up to version 2.11.4

Posted by kinow <gi...@git.apache.org>.
Github user kinow commented on the issue:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---