java - why does buckminster not resolve my passed JVM argument? -

i have jenkins job uses buckminster build eclipse product.

at beginning have "extended choice parameter" "customer" key can selected.

in buckminster configuration use "customer" variable select right cquery:

import '${workspace}/source/scodi-customer/${customer}/server/features/ch.scodi.${customer}.server.feature/site.cquery'

since variable "customer" per default not available in commands, added following "jvm arguments":

-dcustomer=${customer}

this used work well, updated server , build environment java 1.7 32-bit java 1.8 64-bit. since following error trying build:

java.io.filenotfoundexception: [path job]\source\scodi-customer\${customer}\server\features\ch.scodi.${customer}.server.feature\site.cquery (the system cannot find path specified)

before variable resolved fine.
buckminster or java8 problem, not being able resolve ${customer} variable? there maybe (cleaner) way pass variable buckminster configuration?

edit: did further testing , added following jvm arguments, same exception referring missing ${customer}. looks me jvm arguments ignored.

-dcustomer=customer

finally found workaround.

i had rename "customer" variable "customer", resolved in buckminster command area.

from:

import '${workspace}/source/scodi-customer/${customer}/server/features/ch.scodi.${customer}.server.feature/site.cquery'

to:

import '${workspace}/source/scodi-customer/${customer}/server/features/ch.scodi.${customer}.server.feature/site.cquery'

also jvm parameters from:
-dcustomer=${customer}
to:
-dcustomer=${customer}

found out jvm parameters not relevant buckminster command interface used later in "cspex" files.

running jenkins on windows machine might cause issue...
actual problem naming of "extended choice parameter", not being capitalized.