[
https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046939#comment-16046939
]
Florian Hockmann commented on TINKERPOP-1552:
---------------------------------------------
Yes, including it in the {{src}} folder seems really weird considering how the
project is structured. How about adding a dedicated directory for the GLV
generation on the same level as the {{src}} and {{test}} folders? So something
like this:
{code}
gremlin-dotnet (maven module level)
src
test
code-generation (or glv-generation)
groovy-templates
{code}
It is at least common for .NET project to have additional folders on this level
for things like documentation or external tools. And this naming would make it
clear that the folder has a special role and is not included in the .NET
solution. The {{.sln}} file itself shouldn't be a problem here as you have to
explicitly specify which folders and projects should be included.
> 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)
