Just for the clarity sake: these aren't fault injection. The fact that system framework uses code injection doesn't make any fault related. With this said...
mvn-core-install and mvn-fi-install.
no 'fi' should be used in this context. These are system testing related, as you've pointed out quite property.
system intergration tests, which are not yet really officially implemented anywhere
Simply not true: these were regularly executed for y! 0.20 release (oops, have I leaked a corporate secret?). I don't know the state of affairs now though.
For standard development work, the cost of building and deployment can be significant when aggregated, with no benefit.
One of the perhaps not-clear benefits is to guarantee that changes in the system code haven't brake the bindings of the system framework.
I think I'm ok with moving these out of 'mvn-install' target to say 'mvn-system-install'. However, the following should be stated:
- if a code bindings are broken it will bite back at test-patch validation
- deployment of system testing artifacts should remain in 'mvn-deploy' target for the above stated reasons.