1. IMHO introducing an extra dependency should be avoided. Isn't there a way how to copy required functionality into Arquillian? I checked the code of SpringPropertyReplacer and it doesn't seem to have any external dependency.
2. No, it won't. MapObject is used to populate only Container/Container Protocol related configuration. There are plenty of others' such as extension, group, engine, etc. I think this should be implemented directly in config/impl-base so all arquillian.xml elements will be transparently enriched by System properties.
3. Yes, we'll definitely implement this in two steps.
4. Yes, master is the correct branch.
Thanks for the initial implementation!
I will proceed as you have suggested.
Hi Andrew, Aslak and Karel
Please have a look at: https://github.com/rbattenfeld/arquillian-core/tree/ARQ-148
I sent aslak a pull request in order to have a preview on ARQ-148. I will finish this over the weekend.