Hi BJ,
I thought the older versions were delivered by OSGi Alliance, too.
Well, the most problematic in order to upgrade to new artifacts was to deal
with many dependency bundles that have set the old artifacts in its POMs
using "compile" scope (so, bring them as transitive dependency) instead of
using "provided" scope.
To avoid conflicts I had to track and exclude all those transitive
dependencies using:
<exclusions>
> <exclusion>
> <artifactId>org.osgi.core</artifactId>
> <groupId>org.osgi</groupId>
> </exclusion>
> <exclusion>
> <artifactId>org.osgi.compendium</artifactId>
> <groupId>org.osgi</groupId>
> </exclusion>
> </exclusions>
>
I lot of time spent, but seems to be ok now.
best regards
2015-08-18 12:45 GMT-03:00 BJ Hargrave <hargr...@us.ibm.com>:
> 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]
> <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
>
>
>
> ----- 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
> <http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22org.osgi.compendium%22>
> but now it is osgi.cmpn.
> <http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22osgi.cmpn%22>
>
> The same happened with core and annotation jars.
>
> This change was intentional?
>
> regards,
>
> Cristiano
>
> [1] - http://search.maven.org/#search|ga|1|org.osgi
>
> _______________________________________________
> 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
>
--
"Tudo vale a pena se a alma não é pequena..."
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
