Updater: command-line updater does not pick up dependencies automatically

When a new version of, say, `jars/a.jar` all of a sudden depends on `jars/b.jar`, that dependency is apparently not recorded when uploading `a.jar` and `b.jar` via the command-line updater.

Start by locating the command-line updater and its upload path for jars such as a.jar and b.jar. Reproduce an upload where a.jar newly depends on b.jar, then verify that the dependency is recorded automatically; the issue names no specific source file or test.

Written by the indexing model from the issue text.