To me sounds like a huge trade-off if "polute" AeroGear JS is required.
Karel Piwko wrote:
Hi,
one of the possible ways how to fix OpenShift cartridge going idle could be
fixed by deploying the backend to the cartridge right before tests. That way
it would be fresh when running tests.
There is already tooling almost exactly what we need. However, it
would "polute" Aerogear JS with some WAR or whatever Kris needs to be
deployed.
WDYT?
--
abstractj