You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/01 12:27:04 UTC

[jira] [Commented] (TINKERPOP-1552) C# Gremlin Language Variant

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

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

Github user spmallette commented on the issue:

    https://github.com/apache/tinkerpop/pull/600
  
    @FlorianHockmann don't want you to think that this pr was forgotten. there didn't seem to be any objection to merging this pr to a local tinkerpop branch for further collaboration - so that much will likely happen in the more immediate term. longer term, i'm still thinking through options for the overall test framework and for serialization issues glvs are facing. there will be discussion on the dev list around that topic i think (though i i long ago brought up cucumber tests on the dev list as the approach for generalized testing and there were no other suggestions presented, so in a sense we have some consensus there on that avenue of thinking).


> 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
>
> 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)