On Sep 9, 2008, at 9:53 AM, Mike Schrag wrote:
>>>> Does that mean that if one of my frameworks depends on another
>>>> framework, and that framework dependency is exported, both
>>>> Eclipse and
>>>> the <framework> ant element will do the right thing (or at least
>>>> try to)
>>>> and import the dependency in more-or-less the right place in the
>>>> classpath?
>>> It does not currently do this ... This actually requires a change
>>> to the framework formats, because frameworks currently do not
>>> define their dependencies in Info.plist (which they could and
>>> should do). At that point, we could then load the transitive
>>> dependencies for the application and you wouldn't have to define
>>> them manually at the application level. So "not yet" is my
>>> answer. But then, this is no worse than the old way in this
>>> respect.
>>
>> What exactly do you gain by having the depended-upon frameworks
>> flagged as exported then?
> 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.
Thanks
Dave
This archive was generated by hypermail 2.0.0 : Tue Sep 09 2008 - 10:11:44 EDT