> Could it possibly be causing the gems to load in a different order to > normal (hence triggering the error due to some dependency issue?) > > Ed W >
Seems reasonable. When I have a bit more time I'll investigate. In the meantime, I'll just have to keep track of the dependency manually. --T
_______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
