SwingX build broken ... AGAIN, DAMN!!!!
shit happens - but it must not happen every other day.
Some basics (as I see it) to minimize:
* whoever commits has the responsibility to check the build - CC helps a
lot because it will notitfy the committer if anything broke.
* On receiving such a notification, the committer should make it TOP
priority to fix the build. If immediate fix is not possible, the minimum
action should be a notification on the forum, so others don't waste
their time in figureing out what's wrong
* better yet: if a committer can't guarantee to have the time to wait
for build success/failure (after all it's Friday evening), s/he should
wait with the commit until there will be time to cope with the consequences.
This time the first breakage seems to be related to the additions around
MultiGradient, MultiSlider - probably something wrong with the
dependency on the optional jars (which look incomplete anyway,
GroupLayout isn't there).