We were discussing the same when thinking about adding OSGi support to HV. On the downside this adds a dependency on the OSGi API to the core module (which should be optional for non-OSGi use cases), on the other hand one would have one artifact which can be used stand-alone and with OSGi as well.
Correct me if I am mistaken, but we are just talking about an entry in the manifest. That really does not create "a dependency on the OSGi API", does it? In an OSGi environment I assume it gets used. In an non-OSGi environment it would just get ignored no?
Correct me if I am mistaken, but we are just talking about an entry in the manifest. That really does not create "a dependency on the OSGi API", does it? In an OSGi environment I assume it gets used. In an non-OSGi environment it would just get ignored no?