Closed wjwwood closed 11 years ago
Previously if a capability was started, it tried to start the capabilities it depends on without checking to see if they are already running.
Coverage remained the same when pulling 81d45214f30167f4fd49a1a9c908a9972a5f4955 on fix_multi_depends_on into d2c9951f336af86f06e04a2772b498da1f18a026 on master.
Previously if a capability was started, it tried to start the capabilities it depends on without checking to see if they are already running.