I also have this problem. It would appear that the purpose of this function is to import build files that were created by exporting an existing Eclipse java project buildfile. It is not intended to be able to import any random build.xml, which might contain just about anything and could hardly be expected to work. Even relatively simple build.xml's do not necessarily yield projects that "work right" with the eclipse automated builder.

I have the exact same problem as Erik does. A complex root build file that does not contain a javac task defined in the root build file but the sub projects do have a javac task defined. I cannot create an Eclipse project from an existing ant build file. What is the solution?

this solution works only when you have defined a javac task in your build file.

when you have a more complex project structure, with sub projects (every sub project contains it's own build file system) and you have a root build file to build the whole project than this solution does not work.

on my experience eclipse don't walk through the ant tasks in the build file and search for javac tasks through the other build files in the project :(

for any solution about this problem feel free to inform me ;) - mailto:faithnomore@gmx.at