Re: [ecf-dev] Initial upload of jSLP provider to ecf1.osuosl.org
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.).
> Markus: Add appropriate about.html to ECF SLP bundle, checkin provider
> test code (to ecf1.osuosl.org tests module). (bug
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?
> 4) Verify the maintenance strategy for jSLP that Jan (and Markus and Ken
> I suppose) would like to undertake. That is, once we contribute to
> dev.eclipse.org we'll probably have to identify a committer willing to
> maintain the code (e.g. bug fixes, etc). I'm willing to take part in
> this support, but it will probably require either Jan and/or Markus to
> commit to *some small* amount of subsequent support (i.e. fixing of
> critical bugs, etc).
> Scott, Jan, Markus: Figure out a way to maintain jSLP code.
Since jSLP and ECF is used by a product I'm working on at my day job,
count me for jSLP support.
Jan: AFAIK there are no unit tests for OSGi jSLP and the ones for the
standalone version are rather small?
Btw. if we move the jSLP sources, we must not forget about the open bugs
at sf.net. Those have to migrated as well.