[
https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045994#comment-16045994
]
Florian Hockmann commented on TINKERPOP-1552:
---------------------------------------------
I agree that we should publish a first pre-release package soon, but I would
like two add two features first that were recently introduced in the pre-GLV
version of Gremlin.Net:
# [Support for
authentication|https://github.com/FlorianHockmann/Gremlin.Net/pull/7]
# Adding [support for.NET Framework
4.5|https://github.com/FlorianHockmann/Gremlin.Net/issues/9]
But it shouldn't take long to implement those for the current version.
Apart from that we should change the description of Gremlin.Net that will be
displayed on nuget.org to reflect the fact that is no longer just a driver. It
should also explain the current state Gremlin.Net is in of being integrated in
TinkerPop due to the addition of the GLV to avoid confusion between the current
version 0.2.1 and the new version 3.2.x.
> 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)
