You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/11/01 11:52:00 UTC
[jira] [Commented] (TINKERPOP-2085) Remove dependency on Mono
[ https://issues.apache.org/jira/browse/TINKERPOP-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671498#comment-16671498 ]
stephen mallette commented on TINKERPOP-2085:
---------------------------------------------
whoa - thanks for noting this. looking forward to that reduced complexity in the deploy process. it still amazes me that we manage to hold together all these different build systems with maven on single systems.
> Remove dependency on Mono
> -------------------------
>
> Key: TINKERPOP-2085
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2085
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release, dotnet
> Affects Versions: 3.2.10
> Reporter: Florian Hockmann
> Priority: Minor
>
> We currently rely on Mono to push NuGet packages and to create the Gremlin.Net.Template package.
> To push the packages, we can now also simply use [{{dotnet nuget push}}|https://docs.microsoft.com/dotnet/core/tools/dotnet-nuget-push]
> and for dotnet templates, there seems to be [a workaround|https://github.com/NuGet/Home/issues/4254#issuecomment-372795990] that uses a dummy {{.csproj}} file which enables {{dotnet pack}} to create a valid NuGet package for a dotnet template.
> So, we don't have to use Mono any more at all and we also shouldn't need to download nuget.exe any more during the build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)