Description
My use case is I am creating a cross project reusable data library with a MyBatis mapping. What I would like to do is provide, with said library a default config.xml file that can be extended to add additional environments. Most configuration changes that might be required on a project by project basis appear to be able to be easily accomplished via the use of properties files except for the case of adding additional environments.
I have worked around this by creating just a couple default environments, namely a jdbc and a jndi environment for my project and others that may use this, but this is slightly cumbersome. So, it would be nice, if you could specify that a mapping file extends or includes other mapping files or specify multiple mapping files to be read in that override/merge with each other as they are read in.