{"thread":{"id":"18898","subject":"[JGIT PATCH 0/3] JGit in server side environment","startedAt":"2009-04-16T14:01:31Z","lastAt":"2009-04-16T14:01:31Z","messageCount":1,"participants":["Constantine Plotnikov"],"isPatch":true,"patchVersion":1,"patchTotal":3},"messages":[{"id":"111449","messageId":"85647ef50904160701p2d2b729aw7cb3c2f10ca2d17a@mail.gmail.com","threadId":"18898","inReplyTo":null,"subject":"[JGIT PATCH 0/3] JGit in server side environment","fromName":"Constantine Plotnikov","fromEmail":"constantine.plotnikov@gmail.com","sentAt":"2009-04-16T14:01:31Z","receivedAt":"2009-04-16T14:01:31Z","isPatch":true,"sender":{"key":"constantine.plotnikov@gmail.com","avatar":null},"body":"I'm sending a series of the patches that make JGit more suitable for\nusage in on the server-side environment, The patches do the following:\n * It is now possible to supply connection specific functionality for\nSSH transports instead of using single global configuration\n * It is now easier to write a custom session factory that uses\n~/.ssh/config for server-side environment\n\nThe patch consists from the following parts:\n * [JGIT PATCH 1/3] Changed Transport class hierarchy basing on\nunderlying transport\n * [JGIT PATCH 2/3] Moved common SSH related functionality to the base\nclass SshTransport\n * [JGIT PATCH 3/3] Extracted AWT-independent superclass from\nDefaultSshSessionFactory\n\nConstantine\n"}]}