Hi, thank you for the very fast response. I would like to make things a bit more clear. I would like to create separate jars that contains only the relevant packages (e.g. osgi-jdbc.jar, osgi-blueprint.jar, ...)
We have a public maven repository where I would like to upload these jars. Do you have any restriction or recommendation concerning to the maven groupId:artifactId:version naming? The best would be org.osgi:osgi-blueprint:4.2.0 but if you prefer I can think in other grouId first not to occupy the standard one. Regards, Balazs Zsoldos Software Architect Mobile: +36-70/594-92-34 Everit Kft. https://www.everit.biz On Tue, May 8, 2012 at 12:48 PM, Holger Hoffstätte < [email protected]> wrote: > On 08.05.2012 12:17, Balázs Zsoldos wrote: > > Is there any practical reason for this or is there a jar that merges the > two? > > AFAIK this is "historical" (always a nice excuse :) because the APIs > are/were always released together for & with a core framework release. > Other than that there is IMHO no practical reason or benefit, but - as > your posting explains - quite a few downsides. It would be significantly > easier if all official service APIs were released as separate artifacts. > They have clearly separated versions and requirements; except for the core > framework there is IMHO no need for arbitrarily aggregated jars. > > just my 0.01€, > > -h > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
