Upgrade gitlibs. This also address the issue with private keys

[sanel]

tools.gitlibs now uses git directly, instead of Jsch, so workarounds are no longer necessary. Password protected private keys are now handled just like they are done through normal git command.

Addressing #57

[sanel]

I haven't updated README.md and I just tested it against a private github repository, which works without problems.

[reifyrobot]

This PR is being flagged as STALE because it has not had recent activity in the last 60 days. It will be closed if no further activity occurs in the next 14 days. If you believe this repo should be excluded from this process, please add the repo to this list.

[rome-user]

@manderson202 Are there objections to the changes in this PR?

[manderson202]

Hi, thanks for the PR and the feedback here... sorry we haven't been able to get back on this. I did pull down the code and the integration tests failed for me, but I didn't get a chance to troubleshoot why. If you can get the tests passing I can take another look.

[reifyrobot]

This PR is being flagged as STALE because it has not had recent activity in the last 60 days. It will be closed if no further activity occurs in the next 14 days. If you believe this repo should be excluded from this process, please add the repo to this list.

[Sandarr95]

Hi, I've taken a quick look at why the tests fail. It seems to be because the test-project references the version that's set in the PR ("0.4.2"), but that can't be found. Running locally with this PR linked in the checkouts, the tests ran fine. Can I do anything to help move this along?

[rome-user]

Is the version bump in the project.clj needed for the tests to run against this PR? If not, then I think it would be best to remove that version bump, and let the maintainers of this project do it themselves when it's time to cut a new release of the plugin.