[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] OSGi reintroduction to Orbit
|
> Is there something we can do about this issue?
Move this discussion to the Orbit ML and refer to it on the cross-project-ml.
Looking at the example you give, I think that the naming rules that have been applied by Orbit (which are based on the content of the jar) make more sense than using the concatenation of Group id an Aritfact id where you end up with really ludicrous names.
-----Original Message-----
From: eclipse-dev-bounces@xxxxxxxxxxx [mailto:eclipse-dev-bounces@xxxxxxxxxxx] On Behalf Of Krzysztof Daniel
Sent: July-12-13 4:52 AM
To: eclipse-dev@xxxxxxxxxxx
Subject: [eclipse-dev] OSGi reintroduction to Orbit
Hello everyone.
I'd like to describe a problem that started becoming very visible in the last year on the border of Eclipse Community - Orbit.
As more projects adopt OSGi, Eclipse independent projects started adding manifests to their jars. The problem is that their bundles ids rarely match the Eclipse Orbit one. A quite recent example:
javamail 1.5.0 has gid:aid com.sun.mail:javax.mail, which translates into OSGi bundle id com.sun.mail.javax.mail.
The worst part is that it is done according to naming rules. It looks like it is Orbit which is using wrong bundle ids.
This whole situation is quite new and unexpected - at a time there was no maven/osgi naming guidelines and it was fully justified to have Eclipse specific names. Right now they just increase the fragmentation, are a maintenance cost and at the same time they have very limited adoption.
--
Krzysztof Daniel <kdaniel@xxxxxxxxxx>
Red Hat
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/eclipse-dev
