MAVEN_OPTS defined in a stack gets overriden by workspace

[siamaksade]

When defining the MAVEN_OPTS env var via the stack configuration, the workspace overrides the env var.

stack definition:

         ...
        "machines": {
          "dev-machine": {
            "env": {
              "MAVEN_OPTS" : "-Xmx512m"
            },
         ...

And in the workspace:

[user@workspacejegnbkonc07zrzqt projects]$ env | grep MAVEN_OPTS
MAVEN_OPTS=-XX:MaxRAM=150m -XX:MaxRAMFraction=2 -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePoli
cyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xms20m -Djava.security.egd=file:/dev/./urandom

[skabashnyuk]

how can I reproduce this issue?

[ghost]

@siamaksade do you have this env in ~/.bashrc in a container?

[siamaksade]

To reproduce, create a new stack using this json https://hastebin.com/moyifanoji.json and then create a workspace based of this stack.

[siamaksade]

@eivantsov no, it's in the stack json https://hastebin.com/moyifanoji.json L15

[ghost]

@siamaksade ok, you did not want to check it, I did it for you.

In your ~/.bashrc, there's an interesting line:

[user@workspace2ijl3shz90dbzhsh projects]$ cat ~/.bashrc | grep MAVEN
export MAVEN_OPTS=$JAVA_OPTS

If you remove it, your MAVEN_OPTS will be what you expect:

[user@workspace2ijl3shz90dbzhsh projects]$ echo $MAVEN_OPTS
-Xmx512m

Does this answer your question?

[siamaksade]

My image just drives from eclipse/centos_jdk8, which I suppose is doing what you described:
https://github.com/siamaksade/che-jdk-recipes/blob/master/Dockerfile

Thanks for tracing this but this just tracks down the root cause of the reported issue to eclipse/centos_jdk8 overriding defined MAVEN_OPTS.

[ghost]

@siamaksade yes, that line should be removed. I'll take care of it.

[siamaksade]

Created an issue on the che recipes repo:
eclipse-che/che-dockerfiles#204

Closing this one.