[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [orbit-dev] How to name bundles from different implementers?
|
+1 for Dave - javax.mail should go
first.
What about using a different separator to separate the
bundle vendor from the package
name -- e.g. a comma, like in
"javax.mail,glassfish_1.4.1.20080725" -- would commas
in the symbolic name present any problem? There's other
options to, like colon or
parenthesis...
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
I'll go with group consensus, but
was thinking that the pattern of "javax.mail.glassfish" would fulfill the
popular naming convention of "most significant part of the name to the left"
(most significant, that is, with respect to all bundles) ... which has the
side effect of allowing it to be alphabetized more meaningfully (that is, all
the bundles starting with "javax.mail" would some together in a list). Maybe
then, also, we could follow the convention that the provider attribute on
package exports be exactly whatever follows the main package name, just
"glassfish" in this case, making it a little easier to sanity check and
type-in constraints.
Just some
more thoughts.
Thanks,
| From:
| Thomas Watson/Austin/IBM@IBMUS
|
| To:
| Orbit Developer discussion
<orbit-dev@xxxxxxxxxxx>
|
| Date:
| 07/21/2008 09:52 AM
|
| Subject:
| Re: [orbit-dev] How to name bundles
from different implementers? |
My first thought was exactly what Chris mentions with
using export-package attributes. But the bundle symbolic name really should be
distinct so the different bundles can be distinguished from each
other.
My vote is to use the name space of the provider first followed
by the package (e.g.
org.glassfish.javax.mail)
Tom
David M
Williams---07/20/2008 10:42:55 PM---That's what we've done so far, but, in bug
226813 it's been argued that bundle-name + version-numbe
From:
| 
David M Williams/Raleigh/IBM@IBMUS
|
To:
| 
Orbit
Developer discussion <orbit-dev@xxxxxxxxxxx>
|
Date:
| 
07/20/2008
10:42 PM
|
Subject:
| 
Re:
[orbit-dev] How to name bundles from different
implementers? |
That's what we've done so far, but, in bug 226813
it's been argued that bundle-name + version-number has always been presented
as "one set of bits".
| From:
| "Chris Aniszczyk"
<caniszczyk@xxxxxxxxx>
|
| To:
| "Orbit Developer discussion"
<orbit-dev@xxxxxxxxxxx>
|
| Date:
| 07/20/2008 09:06 PM
|
| Subject:
| Re: [orbit-dev] How to name bundles from different
implementers? |
The suggestion has been made,
to include "vendor" name in the bundle ID (as well as name an attribute on the
export package statements).
Can't we make the
BSN to just be the package space and include the vendor info on export package
statement?
In CVS, we can store things like
javax.mail.{vendor}
This way at least, people are kind of forced to use
Import-Package with attributes if they want a specific implementation. That is
one of the strengths of attributes.
In the end, we should come up with
a policy on this issue soon as I can see it coming up more in the future.
--
Cheers,
~ Chris Aniszczyk _______________________________________________
orbit-dev mailing
list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev
mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing
list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
