@Thomas we will definitely try to work under the "JBossOSGi umbrella" if I understood what that means
As for audiences, we already anticipated most of this during our work for 4.0 with the break down into 3 distinct package structures:
API for code we expect application code to bind against
SPI for code we expect integration code (either ours or others) to bind against
INTERNAL for code that is for our internal use.
For the most part that package break down should line up perfectly well with your audience breakdown.
Not following your bit about "pay attention to the OSGi version scheme" and exporting. Maybe you could elaborate a bit? Hard to "pay attention" to details one does not understand
@Thomas we will definitely try to work under the "JBossOSGi umbrella" if I understood what that means
As for audiences, we already anticipated most of this during our work for 4.0 with the break down into 3 distinct package structures:
For the most part that package break down should line up perfectly well with your audience breakdown.
Not following your bit about "pay attention to the OSGi version scheme" and exporting. Maybe you could elaborate a bit? Hard to "pay attention" to details one does not understand