GitHub user PommeVerte opened a pull request:

    https://github.com/apache/incubator-tinkerpop/pull/270

    TINKERPOP-732 - tree() serializing over GraphSON

    I've had to upgrade jackson in `gremlin-shaded` to version `2.7.2` for this 
fix. I've made the appropriate changes to the `NOTICE` files.
    
    This makes `tree()` work with the `GraphSON` serializers. I've added tests 
for `GraphSON` and `Gryo` + driver tests for `GraphSONMessageSerializer` and 
`GraphSONMessageGremlinSerializer`
    
    What I've done for testing:
    - `mvn clean install` **OK**
    - `mvn verify -DskipIntegrationTests=false -pl gremlin-server` **OK**
    - Ran tests with the php driver against `application/json`  **OK** 

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

    $ git pull https://github.com/apache/incubator-tinkerpop TINKERPOP-732

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

    https://github.com/apache/incubator-tinkerpop/pull/270.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 #270
    
----
commit c01f19708a56452c368919133bee38c0e00bd3a2
Author: Dylan Millikin <dm...@apache.org>
Date:   2016-03-16T16:32:44Z

    TINKERPOP-732 added support for tree() results to be serialized over 
GraphSON

commit edb61f5e356dc30fc75a318bbf41e887f6bd361b
Author: Dylan Millikin <dm...@apache.org>
Date:   2016-03-18T03:11:30Z

    Added mentions to notice. Added tests and made a slight correction to 
serialization

commit 2f32f0cf0e158a1a8a2c4fbdc4956bf4fd29fa14
Author: Dylan Millikin <dm...@apache.org>
Date:   2016-03-18T05:02:38Z

    removed some commented code

----


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

Reply via email to