Ninju, Thanks for the reply. I tried forking the javac too, but got the same results. I'm leaning more and more to thinking the problem is in the foo build itself, and maybe the foo code. I found unused imports that caused the EJB dependency, but taking them out lead to another EJB dependency that I haven't been able to track down. I added wlclient.jar to the javac's classpath and the EJB dependencies didn't cause trouble any more. But of course this just makes me wonder more, why did the build work without that jar if run on its own? Somehow the EJB files get in the classpath but I haven't worked it out yet.
After putting wlclient.jar in the classpath, the common.compile target works. But another target fails that uses servicesgen (a WebLogic ant taskdef). Ant doesn't complain about the taskdef line, just when servicegen is used. This makes me think the wrong weblogic jar is used in the taskdef, so I'm going to try changing that next. (It might also explain why the javac classpath doesn't need the wlclient.jar when not using a wrapper build file.) Thanks again, boz
