Hmmm if this is failing now in 1.9, it should be also failing in 1.8, as there haven't been changes to this stuff IIRC. We can assume then that there are no such scenarios "in use", so I'd say this discussion is enough to go ahead.
Given that this hasn't been a reported issue till now, I'd agree to merge the fix that forces the use of netcat. In the end, if the other possible connectors are not tested, we shouldn't officially support them, and if at some point we have to, we should make sure it works as expected everywhere, including the CLI. So I'd say, go ahead and merge the PR :) On 8 April 2015 at 00:00, Andrew Phillips <aphill...@qrmedia.com> wrote: >> If we merge this pull request we might be *removing* working stuff. > > > That is true, but the question here is whether that stuff was ever > *intended* to work. It's certainly not been tested, from what I recall - the > reason we originally didn't try to figure out how to get all the bundles > loaded in Karaf because we decided that we only wanted/needed to support > ssh-agent over netcat. > > How about sending an email to user@ to see if any other agentproxy scenarios > are in use? If so, then we can indeed consider the custom ConnectorFactory > approach involving classloading that you described. > > Regards > > ap
