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

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

GitHub user FlorianHockmann opened a pull request:

    https://github.com/apache/tinkerpop/pull/629

    TINKERPOP-1552: Clean-up Gremlin-DotNet project files

    https://issues.apache.org/jira/browse/TINKERPOP-1552
    
    This removes some obsolete configuration options and improves the package 
meta information. Especially the description was extended to reflect the 
current state of Gremlin-DotNet. This explanation can be removed as soon as the 
old Gremlin.Net driver is obsolete (probably when a first release version of 
Gremlin-DotNet is released).
    The version is now 3.2.5-beta1.
    
    I also enabled the generation of an XML document containing the 
documentation comments which will be displayed to the user with IntelliSense. 
The warning about missing comments had to be disabled for some files as we 
currently just don't have comments for those. I think that's ok for now, but we 
should try to find a way to create meaningful comments where they are missing 
right now for the first official (non-beta) release.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/FlorianHockmann/tinkerpop 
gremlin-dotnet-packagemetadata

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tinkerpop/pull/629.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #629
    
----
commit 02955d4df4c1e16ec3fcd6977979badc44a8b91e
Author: Florian Hockmann <[email protected]>
Date:   2017-06-15T16:25:56Z

    Clean-up Gremlin-DotNet project files
    
    This removes some obsolete configuration options and improves the package 
meta information. Especially the description was extended to reflect the 
current state of Gremlin-DotNet. This explanation can be removed as soon as the 
old Gremlin.Net driver is obsolete (probably when a first release version of 
Gremlin-DotNet is released).
    The version is now 3.2.5-beta1.

commit ab55e95de63efc6d670a7af50901f9c48a33501d
Author: Florian Hockmann <[email protected]>
Date:   2017-06-15T17:00:38Z

    Let Gremlin-DotNet include the documentation comments
    
    Every build now generates an XML document containing the documentation 
comments which will be displayed to the user with IntelliSense. The warning 
about missing comments had to be disabled for some files as we currently just 
don't have comments for those.

----


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

Reply via email to