Yes, the change was intentional. This is the first time that the OSGi Alliance itself released the companion code jars to maven central. We now build the necessary maven metadata as part of the regular OSGi builds thanks to maven support improvements in bnd. As part of this, we regularized the artifact id to be identical to the Bundle-SymbolicName of the jar. Prior to this release, 3rd parties put the OSGi companion code jars in maven central and they unfortunately used an improper artifact id.
[I gave this same answer in http://blog.osgi.org/2015/08/release-6-of-osgi-compendium-osgi.html?showComment=1439468504763#c7602007936621922721]
--
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
hargr...@us.ibm.com
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
hargr...@us.ibm.com
----- Original message -----
From: Cristiano Gavião <cvgav...@gmail.com>
Sent by: osgi-dev-boun...@mail.osgi.org
To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
Cc:
Subject: [osgi-dev] Why new OSGi jars were published with different names at maven central ?
Date: Tue, Aug 18, 2015 10:51 AM
Hi,I read yesterday that the new release of compendium was published. Great!
Then I create a new version of my parent pom and upgrade the versions to 6.0.0. But I got a error.
So I went to maven central site[1] in order to check if the compendium jar was there already and noted that it is there, but has a new name from now.
It used to be org.osgi.compendium but now it is osgi.cmpn.
The same happened with core and annotation jars.
This change was intentional?regards,
Cristiano_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
