Maybe you could have a "config.dirs" property with a default value of "jetty.home,jetty.base"
Let users override it to anything they want as long as jetty.home is first and jetty.base is last. (Not sure if that would necessarily be required but it might be easier to just enforce that for the time being. )
To use your example:
config.dirs=jetty.home,corp.common,devops.common,project.common,jetty.base
You would need other properties with directories as values for corp.common, devops.common, and project.common.
If you defined this property on the command-line or in the jetty.base config then you could have different sets of config for different servers (in case some servers didn't want config from a particular shared location).
This is an open feature request.
The jetty-9-alpn branch (aka the jetty-9.2 branch), has reworked the file
lookups, and are in a better place to support shim directories (sorry,
don't have a better name for them) in the future.
So that the lookup could logically look like something of the following ...
${jetty.base} = /opt/apps/self-serve
${project.common} = /opt/groups/web-group
${devops.common} = /opt/devops/devops-common
${corp.common} = /opt/corp/legal-common
${jetty.home} = /opt/jetty/jetty-distribution
Would welcome some discussion on a good way to accomplish it.
I think having the directories also be associated with a property name is
important (for various lib or xml lookups)
