Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/867
Rebased and I extended the `gremlin-archetypes` section in the reference
docs by splitting it into two sections: _Maven Archetypes_ and _Gremlin.Net
Template_. In the future, we can add more sections when the other GLVs also get
templates. `gremlin-archetypes` is now the anchor of the _Maven archetypes_
subsection.
However for some reason the generated docs have an added comment in the
last listing and I don't know how I can prevent that from happening. It looks
like this:
```bash
dotnet new gremlin -o MyFirstGremlinProject
// LAST LINE
```
> do you just mean that the dotnet-maven-plugin call to pack doesn't work
Unfortunately not, it simply doesn't work with the dotnet CLI tool. So
there really isn't anything the plugin can do to help us here. Here is [what
the dotnet docs
say](https://docs.microsoft.com/en-us/dotnet/core/tools/custom-templates#packing-a-template-into-a-nuget-package-nupkg-file)
about that:
> Currently, a custom template is packed on Windows with nuget.exe (not
dotnet pack). For cross-platform packaging, consider using NuGetizer 3000.
I never used (or heard about) this NuGetizer and it looks a bit outdated.
So I'm sceptical whether that could help us.
> Maybe we could wait until dotnet toolchain supports packaging and pushing
templates (is there a ticket for it?), instead of increasing the complexity of
the deploy process by requiring Mono.
Unfortunately, I don't think that the dotnet CLI tool will support that any
time soon. The ticket in question should be Nuget/home#4254. It has 20x ð,
was created over a year ago, but it doesn't look as if they wanted to address
this issue in the near future.
Nevertheless I share your concern that we shouldn't make the build too
complicated, especially for new contributors who just want to submit a PR.
Shouldn't it be possible to build the .NET projects from Maven and execute
their tests without having to execute the `package` phase? I just tried it with
`mvn clean test`, but that didn't execute any tests to my surprise.
You mentioned that you don't want to increase the complexity of the
_deploy_ process, but that already required Mono even without this PR. Or at
least that's what the dev docs currently say:
> For those who will release TinkerPop, it is also necessary to install
Mono.
When we decide that we don't want to add this template right now, then I
could also host it from my own GitHub until `dotnet pack` works with templates.
The downside with that approach is of course that it would be harder to find
the template, especially for new users who need it in the first place.
---
