| Re: [ecf-dev] Initial upload of jSLP provider to ecf1.osuosl.org |
|
Hi Markus, Markus Alexander Kuppe wrote: Scott Lewis wrote:1) In the short term (next week), we (Markus, myself, and Ted) work to add the SLP provider to the osuosl build, by retriving the current jslp bundle (at http://downloads.sourceforge.net/jslp/jslp-osgi-1.0_RC1.jar) during build (via map file http fetch...like we do now with Orbit httpclient). We will use the current version of jSLP (1.0M2) and distribute both the jslp jar binary and Markus' SLP provider bundle via a new osuosl feature (e.g. org.eclipse.ecf.provider.). Actions: Markus: Add appropriate about.html to ECF SLP bundle, checkin provider test code (to ecf1.osuosl.org tests module). (bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=206181)ACK, will start working on it soon. Btw. I want to create a seperate test bundle for JMDNS too and move the JMDNS related tests from test.discovery there. The test.discovery tests would then test discovery SPI independent of a specific provider. Any objections, otherwise I'd start creating a patch? No, no objections. In fact, I propose that we start having provider-specific test code in new test bundles of the form: org.eclipse.ecf.tests.provider.<providername> e.g. org.eclipse.ecf.tests.provider.jmdns Also we can create a new provider test support bundle and move common provider test code into it. It will be called org.eclipse.ecf.tests.provider Scott |