On Sep 19, 2011, at 2:48 PM, Paul Hoadley wrote: Hi Chuck, On 20/09/2011, at 2:49 AM, Chuck Hill wrote: That is, it can't find JavaMemoryAdaptor.framework when it needs it. I'm having this problem when running unit tests in both application and framework bundles of my own. JavaMemoryAdaptor.framework is on the .classpath (confirmed by running 'ant -v'),
The jar file in Resources/Java is on the classpath? That is what gets used to locate the bundle.
Yes. This is in Ant's classpath as it's running the test case:
/Users/paulh/tmp/WT/workspace/Root/Library/Frameworks/JavaMemoryAdaptor.framework/Resources/Java/JavaMemoryAdaptor.jar <snip>
Paul -
Whenever I have had this sort of problem, I usually end up switching the <junit> target to a <java> target. The re-write one has to do for that, the re-jiggering of the parameters, usually points me to the problem. It is kind of labor-intensive, but it works. Once it works as a <java>, I have seen the error and it will work as a <junit>. Also, spending some more time looking at the verbose output from ant helps. It just takes longer than it seems is justified. It is extremely verbose. But, you know, the problem is always in there somewhere and if you read the warnings, it is usually describing the problem, even if the warnings seem to be coming from out of left field.
Also, typos in path names lead to hours of fun. The Resource directory is one of my faves. And mixed-case terms when unexpectedly on a case-sensitive file system.... There are lots of things to choose from.
good luck - ray
|