[
https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033461#comment-16033461
]
stephen mallette commented on TINKERPOP-1552:
---------------------------------------------
> (By the way: It would be a good idea in my opinion to list Gremlin.Net on the
> TinkerPop page so that new users start with that driver instead of the
> abandoned Teva Gremlin.)
[~Florian Hockmann] Didn't realize Teva was abandoned, nor did I realize that
Gremlin.Net wasn't listed. Perhaps you could bring that up on the dev list as a
DISCUSS thread so we can build consensus on what to do.
> IMO it would be nice to have a single assembly per nuget package, but that's
> a personal preference for a project this size.
[~jorgebg] are you proposing this structure:
{code}
gremlin-dotnet (maven module level)
src
Gremlin.DotNet
Driver
Process
Structure
{code}
All of that is C# then if there is a need for VB or F# specific odds and ends
you would just do:
{code}
gremlin-dotnet (maven module level)
src
Gremlin.DotNet
Driver
Process
FSharp
VB
Structure
{code}
if so, is that typically how mixed language projects organize in the .NET
world?
> We could make a different nuget package for the driver implementation but
> that's optional.
I think we can follow gremlin-python on this for now and make it just one nuget
package.
Nice discussion everyone - thank you
> 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)
