In the latest nightly, there is a change to the way framework
dependencies work to more closely match the way WO deployment works.
In the new build, if you do not export framework dependencies from
your frameworks (which is the default), you application will no longer
include them in the runtime classpath. This more closely matches the
way WO works, which is that it does not understand nested
dependencies. So in the new nightly you will need to declare your
framework's dependencies in the application. On the bright side, if
your app breaks, it would have broken in deployment, too, so this is a
pretty good change. A better change would be to support nested
dependencies, but this would require both a change to the framework
Info.plist (to declare dependent framework names), embedding (to
include nested dependencies), and the code that constructs the runtime
classpath (or a change to WOBoostrap to load nested automatically
rather than declare them in the macosxclasspath file).
ms
This archive was generated by hypermail 2.0.0 : Thu Nov 06 2008 - 14:19:25 EST