Hi Yetus devs, Looking for a bit of guidance on how to properly setup modules for test-patch executions.
At my day job we were using Yetus for a maven project and accidentally broke our test patch job by accidentally misconfiguring the path to maven binaries. This didn't get caught because the patch was changing the personality file but no java source was changed. So when we tried to be "smart" and "efficient" we skipped all the actual maven steps and didn't catch that the binary was broken until the next patch failed in mysterious ways. Does it make sense to always run a maven goal? mvn_install? mvn_deps? Not sure what we would actually need. Is this something that we should address in our personality or is this generally useful? Possibly related - we're still on 0.4.0, so if this same behavior has been fixed by default in a newer version that's an easy solution too. Thanks, Mike
