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

ASF GitHub Bot commented on TINKERPOP-1552:
-------------------------------------------

GitHub user jorgebay opened a pull request:

    https://github.com/apache/tinkerpop/pull/622

    TINKERPOP-1552: Remove unintended comment

    

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

    $ git pull https://github.com/jorgebay/tinkerpop csharp-glv-generics-fixes

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

    https://github.com/apache/tinkerpop/pull/622.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 #622
    
----
commit 7c7511bb868ca78a4e94ae2a1d507afa2ec87c65
Author: Jorge Bay Gondra <jorgebaygon...@gmail.com>
Date:   2017-06-09T08:20:55Z

    Remove unintended comment

----


> C# Gremlin Language Variant
> ---------------------------
>
>                 Key: TINKERPOP-1552
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1552
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: language-variant
>    Affects Versions: 3.2.3
>            Reporter: Jorge Bay
>            Assignee: stephen mallette
>
> It would be nice to have a C# GLV that runs under .NET Framework 4.5+ and 
> .NET Core.
> The maven build could use the Exec Maven Plugin to exec .NET Core's [dotnet 
> test|https://www.microsoft.com/net/core#macos] command.
> Some requirements, from the mailing list (edited):
> {quote}
> 1. The GLV should keep in line with class/method names of the java API
> where possible to ensure consistency of feel across languages.
> 2. There needs to be adequate tests (we're still discussing the approach to
> testing GLVs and i think that needs to be tackled sooner than later as more
> GLVs start to come in). Those tests should produce xunit style output
> unless there is some good reason not to.
> 3. There needs to be adequate documentation (e.g. Reference docs)
> 4. The build/deploy process needs to be bound to maven which might be one of 
> the trickier bits to deal with.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to