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

Florian Hockmann commented on TINKERPOP-1731:
---------------------------------------------

The error occurs in this line already:

{code:java}
def csprojTemplate = engine.createTemplate(new 
File('${project.basedir}/glv/Gremlin.Net.csproj.template')).make(["projectVersion":versionToUse])
{code}

So in {{csprojTemplate}} all problematic characters are already replaced by 
{{\?\?\?}}. I think that we need to configure the template engine itself to 
work with UTF-8. In 
[GROOVY-7144|https://issues.apache.org/jira/browse/GROOVY-7144], someone has a 
similar issue and they also mention ways to configure the encoding of the 
template engine. Unfortunately, that seems to only work for the 
{{MarkupTemplateEngine}} they are using.

{quote}
Either way docker still isn't building for me (same error) for whatever reason.
{quote}

Reading your error message from above again, it looks like this could be 
actually a different issue than the one I had with the broken project file. 
{{Cannot run program "dotnet"}} sounds like the .NET Core SDK is simply not 
installed. Could you check that by executing {{dotnet --info}} in the Docker 
container?

> Docker build does not appear to work for gremlin-dotnet
> -------------------------------------------------------
>
>                 Key: TINKERPOP-1731
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1731
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: build-release, dotnet
>    Affects Versions: 3.3.0
>            Reporter: stephen mallette
>            Priority: Critical
>
> Docker won't build the gremlin-dotnet stuff. I pulled out the {{.glv}} files 
> from that module so that docker would run properly until this can be fixed:
> https://github.com/apache/tinkerpop/blob/2d30a76aabdd009b9b926f83df2308b7578571c0/docker/scripts/build.sh#L71-L72



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to