tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TINKERPOP-1836) .NET sample project
Date Mon, 11 Jun 2018 13:22:00 GMT

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

ASF GitHub Bot commented on TINKERPOP-1836:

Github user spmallette commented on the issue:

    I tend to agree with @jorgebay unless there is some high risk of something breaking in
the template packaging (as i understand it we need nuget so that we can do `nuget pack`) on
release day when we actually execute the `deploy` phase. If it fails on release day that would
be really bad because we'd already have a positive closed VOTE thread and we would already
be half of the other artifacts would have already been deployed. 
    If @FlorianHockmann can explain why there is sufficient risk for failure during `nuget
pack` perhaps we can agree to make that process a documented "Pre-flight Check" step of the
release process that is triggered manually with `mvn clean install -Dnuget`. That way we can
test it ahead of VOTE and not have it be part of the regular build process. 

> .NET sample project
> -------------------
>                 Key: TINKERPOP-1836
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1836
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: dotnet
>    Affects Versions: 3.2.6
>            Reporter: stephen mallette
>            Assignee: Florian Hockmann
>            Priority: Minor
> Create a sample project that can help get users started with .NET and Gremlin. Should
probably be added to the series of gremlin-archetype projects. It seems .NET already has something
analogous to archetypes with "dotnet templates". I'm not sure how those work or are built/deployed/distributed
but we would probably want to ensure that those aspects are somehow still handled by maven
if we can.

This message was sent by Atlassian JIRA

View raw message