It continues to amaze me that we have any sort of reasonably build process
with all of these GLVs in play with all our different environments. Nice
job to everyone who has played some role in designing/testing/fixing our
various builds in their respective ecosystems.
On Sun, May 6, 2018 at 9:03 AM
An update to dotnet/mono came in over night and I can build natively on F27
again. Yay.
$ dotnet --info
.NET Command Line Tools (2.1.105)
Product Information:
Version:2.1.105
Commit SHA-1 hash: fe590c614c
Runtime Environment:
OS Name: fedora
OS Version: 27
OS Platform: Lin
I have tried a great number of things on Fedora 27 but to no avail. Docker
works after rebuilding the image and that should be sufficient.
Robert Dale
On Thu, Apr 26, 2018 at 1:29 PM, Florian Hockmann
wrote:
> That's really strange. I don't know why you see a difference between
> 'dotnet bulid
That's really strange. I don't know why you see a difference between
'dotnet bulid -c Release' and just 'dotnet build' which is the same as
'dotnet build -c Debug' as both should be signing the assembly.
Does it work now with just 'dotnet clean' and 'dotnet build -c Release'
or do you always need
This is on tp32 HEAD.
I think what you suggested helped go in the right direction. First, I have
to 'mvn clean' . Then dotnet clean and dotnet build works.
If I run 'dotnet build' without 'mvn clean', it fails.
The difference appears to be when maven executes, maven calls it as 'dotnet
build -c R
I don't see anything you could be missing there. It should really just
work when you have the right version of the .NET Core SDK.
Since you seem to be using Fedora 27, did you follow the instructions
from here?
https://www.microsoft.com/net/download/linux-package-manager/fedora26/sdk-2.1.101
Alth
Trying to build the docs but I get a .Net error. I followed
http://tinkerpop.apache.org/docs/3.2.8/dev/developer/#dotnet-environment
and installed dotnet-sdk-2.1-2.0.6-2.fc27.x86_64.rpm
$ dotnet --version
2.1.101
$ mvn clean install -Pgremlin-dotnet -rf :gremlin-dotnet-source
I get this error:
