turns out this issue is "just" for the problem of "running all test at
then yes most likely not a showstopper for M3 as long as normal test runs, but please take
a look since some of these issues does look weird.
Most of the problems does though look like its attempting to run *all* tests no matter if
their original submodule have specific configuration for them.
ie. the WS ones missing JDK 5 setup.
The bot ones should all be assigned to QE since they own them - and those might be the
only one able to run properly like this if local test module settings aren't applied
On Aug 13, 2011, at 02:38, Max Rydahl Andersen wrote:
JBIDE-8734 have a bunch of subtasks assigned to be fixed in M4 - some even been marked as
resolved against M4.
Even though trunk is still M3.
I completely missed all these issues until now because they were targeted M4 - i'm
going to bulk update them to M3 and reassign those that are pointing to me to my best
guesses while i'm away.
And for those who have closed issues as fixed in M4 - please fix that too.