AFAIK, where exporting is (was?) important is for jars that are inside
a framework. If you did not export them, then apps that linked to
those frameworks would not "see" the jars that the framework contained.
Kieran
On Sep 9, 2008, at 10:37 AM, Mike Schrag wrote:
>>> Nothing but lying to yourself, though technically all framework
>>> dependencies should be exported all the time and the build system
>>> should figure that out.
>> So it's a Best Practice and should always be done even if, for now,
>> it doesn't really do anything for you because the build system has
>> no way of knowing what dependencies the exported frameworks may
>> themselves have due to the info.plist not having the information in
>> it.
>>
>> I think that's what you just said, but I want to be sure.
> pretty much
>
> ms
>
This archive was generated by hypermail 2.0.0 : Tue Sep 09 2008 - 11:11:55 EDT