Binaries don't go on a repository. Repositories do diffs for version control. A diff doesn't make sense on a binary, so every time you put in a new binary (e.g. jar), it adds another mb of diff to the repository (assuming the binary is 1 mb), so whenever someone tries to checkout or otherwise work with the repository, they have to download the entire history, which includes every single version of every single binary that ever existed in the repository.
Our packaging system uses simple urls (and a hash). This means that it doesn't matter where you put the binary, as long as you link it and provide an updated hash. We've just been using dropbox since it's been the most convenient option for us. I think Josh has indicated that he wants to see the server itself build and deliver the binaries, and I think this is a good idea as well, it's just that it is a bit of an undertakin since building LateralGM and the Plugin is not a very automatible task.
Also, our packaging system partitions everything into individual binaries, so you don't need to upload everything at once. If you build LGM, you only upload LGM, and update the url (if necessary) and hash.