How to segregate imports of module being 'aware of' away from Spring wiring?

@dkayiwa, not really just right now as I have been testing multiple things locally. Thanks for offering to look tho. I know that there are workarounds, and that I can achieve to have a working version using a one or another.

But I’m testing the waters here:

  • Would it be possible to enrich the test framework? (this thread).
  • Is it sensible to extend @OpenmrsProfile's behaviour? (that other thread).
  • If both the above can be considered, could I use both for our real world case: AH aware of Ext I18N?
  • Is that acceptable for the maintainers of AH?
  • Could that pave the way for a very similar approach in Bahmni Core?

@mogoodrich, I’m glad to read that you guys would consider adopting Ext I18N as you said. However let’s keep in mind that Ext I18N is a workaround in itself. I would wish for higher versions of the Core (3.0?) that would not necessitate it anymore, In that light it makes sense to keep it as an optional artifact, with everything running smoothly when it’s not there.