Mike Milinkovich wrote:
As pointed out in the Oscar project proprosal, OSGi forms the basis of the
Eclipse Rich Client Platform. Eclipse is a well-known and growing open
source community in its own right, and we would be very interested in
discussing how the Eclipse OSGi team and the Apache Oscar team can
co-operate.
[ ...partially deleted... ]
We feel that all of these goals could be greatly accelerated by working
together rather than in parallel.
Yes, I too think it would be great if our two communities could find
some way to work together. Clearly, we share common goals, since we are
implementing the same spec. However, this does not mean that all of our
goals are shared.
The point of projects like Oscar and Knopflerfish is purely to support
OSGi technology and the community around it. In this case, I believe
that this makes these communities a better place to focus the OSGi
effort, because it is their primary concern. Ultimately, Oscar and KF
support all aspects of OSGi and are interested in all use cases around
it, all standard services, defining new services, etc. I would assume
that the primary use case driving the Eclipse OSGi implementation is to
support the Eclipse runtime (which makes sense).
Further, positioning an OSGi project at Apache also makes sense to me,
because (from my perspective) Apache specializes in middleware and
enabling technology and OSGi technology falls into this category.
I do believe that this technology will mature to a point where a merge
will be possible, but I do not believe that this time has arrived yet. I
believe that the community still benefits from having different
implementations with different perspectives.
A goal for our communities should be to find the areas where
collaboration makes sense, so that we don't needlessly waste resources.
-> richard
