[ https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046911#comment-16046911 ]
stephen mallette commented on TINKERPOP-1552: --------------------------------------------- I would like to get rid of {{gremlin-dotnet-generator}} and replace it with the revised approach to glv generation which uses Groovy templating. Nicer than string concatenation imo and better than a special java module in the case we have here. in {{gremlin-python}} the templates are just a java resource, but we don't have that structure in {{gremlin-dotnet}}. Adding {{gremlin-dotnet/src/main/resources}} seems weird. I guess it could just be done and the .sln could just ignore that directory, but i dunno - seems wrong. Where would "groovy templates" live in a .NET project? > 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.4.14#64029)