Re: [orbit-dev] Orbit's stance on uses directives

[David M Williams <david_williams@xxxxxxxxxx>]

I think our "stance" if we have
one, is if it is known to be important, to take advantage of it. 
That is,  you can and should open
a bug to add it to in the specific bundle(s) where you think its important.


Its a vague memory, but I seem to recall
someone saying long ago we probably did not want to 
always use it for every bundle, just
out of routine, since it might have a negative impact on 
performance ... especially in cases
where projects/products had a huge number of bundles. 

Does that help? Or are you saying every
bundle would have have to do it, to help your use-case? 




From:      
 Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>
To:      
 orbit-dev@xxxxxxxxxxx,

Date:      
 06/11/2013 02:02 PM
Subject:    
   [orbit-dev]
Orbit's stance on uses directives
Sent by:    
   orbit-dev-bounces@xxxxxxxxxxx

---

Hi,

since I (and my Import-Packages) just got bitten by the fact that the
com.google.gson bundles in Orbit don't employ uses directives, despite
c.g.g.reflect.TypeToken.getType():c.g.g.Type being in the bundle's
public API (my bundle's Import-Packages bound to TypeToken and Type from
different bundles), I wonder what Orbit's stance on uses directives is?

>From what I can see, many bundles in Orbit don't use them and I couldn't
find anything in the Export-Package guidelines [1], either.

So, are missing uses directives considered bugs? Or should I simply
switch to Require-Bundle and shut up? ;-)

Best regards,

Andreas

[1]
<http://wiki.eclipse.org/Adding_Bundles_to_Orbit#Export-Package_guidelines>
-- 
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_________________________
______________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev