|Re: [ecf-dev] ssl-based generic provider|
One question for Markus and/or Wim: Do we have a CA-approved cert on our build machine at OSUOSL? Reason I ask...it would be helpful to be able to test this new provider in an actual use scenario...where the server has a CA-approved cert, so that clients...with a 'normal' cert store...can connect to the server.
Thanks, Scott On 12/29/2012 10:16 AM, Scott Lewis wrote:
Hi Folks, I've been working on a contribution to address this bug: Create generic provider that uses SSL transport https://bugs.eclipse.org/bugs/show_bug.cgi?id=391677I've almost got it going/ready for testing, etc., but wanted to notify the community about one implication: The bundle org.eclipse.ecf.provider (where the generic provider is located), currently has a minimum execution environment set to CDC 1.1. The addition of this ssl-based generic provider requires that the minimum EE be set to jre 1.4 (because of dependence on javax.net, which is not included in CDC 1.1).I don't really know of any consumers that are using CDC 1.1 any longer, so perhaps this affects no one, but I wanted to make sure before I make the change. If you are a consumer of ECF (this bundle) that is using CDC 1.1 then please let us know.Thanks, Scott _______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ecf-dev
Back to the top