@grkvlt, it's to allow the configuration to be specified in brooklyn.properties. I use the code `getManagementContext().getConfig().getConfig(CLASSPATH);` to fetch from properties if it is not configured on the entity - this method needs a ConfigKey. So I would be forced to either have one config key taking String, or to have two config keys, one for String and one for List<String>. I think this way is the lesser of two evils.

Of course if there's a better way I hadn't considered, then I am listening :smiley: