Since the overall response has been positive (even though I am mostly in
the "excess cruft" camp with Eric), I have gone ahead and added it.
Besides other peoples' positive reaction, my feeling is that if people
aren't using iPOJO, DS, etc, then it is better to encourage people to
use ST than trying to do service management by hand, because they will
definitely make mistakes. However, in its current distribution form it
is difficult to use ST, since it is buried in the compendium bundle that
also has dependencies on other packages.
Of course, BND could solve this by having people just pull ST into their
bundle. But if everyone were to do this, then the savings we see by not
having ST in the framework JAR would be quickly outweighed by the
multiple copies of ST embedded into all of the bundles that use it.
We'll try it for now and see how it goes! :-)
-> richard
Richard S. Hall wrote:
Should Felix start including ServiceTracker in the framework JAR file?
Up until now, it has never been included because the framework doesn't
use it, so it is just extra cruft and can easily be downloaded
separately. However, it appears that other frameworks make it
available by default.
Thoughts?
-> richard
