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

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

I finally found the cause for this: The {{Gremlin.Net.csproj.template}} was 
encoded in UTF-8 and contained a [byte order mark 
(BOM)|https://en.wikipedia.org/wiki/Byte_order_mark]. Apparently the Groovy 
template engine has a problem with some special characters like this and 
replaces them with {{\?\?\?}} during the docker build. That resulted in a 
csproj file that had {{\?\?\?}} as the first characters right before the 
license header comment which is of course not a valid XML file anymore.
I just pushed 
[3bf128ae9f9d6f73675705a958b7b4102572eaaa|https://github.com/apache/tinkerpop/commit/3bf128ae9f9d6f73675705a958b7b4102572eaaa]
 which simply removes the BOM bytes from the template file. This fixes the 
build of Gremlin.Net with Docker.

Unfortunately the csproj file still contains some {{\?\?\?}}, e.g., 
{{TinkerPop™}} becomes {{TinkerPop\?\?\?}} and {{application’s}} becomes 
{{application\?\?\?s}}. So we should probably find a way to tell the template 
engine to always use UTF-8 as the encoding which should fix this problem 
completely.

> 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