[
https://issues.apache.org/jira/browse/TINKERPOP-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480904#comment-16480904
]
ASF GitHub Bot commented on TINKERPOP-1836:
-------------------------------------------
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/867
@FlorianHockmann i don't know if any of the following makes any sense, but
would it be crazy to only package templates on deploy (since mono is already
required there)? or do we need to continually build it because it could break
or fail tests (i.e. maven archetypes are built and also tested for problems on
every build)? Or, would it be crazy to only package templates if mono is
present? Or perhaps it is somehow otherwise an optional aspect of the build
(except on deploy)?
> .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
(v7.6.3#76005)
