This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Ranchers, I'm using Eclipse 2.1 with its Ant 1.5 core plugin, and the javadoc target fails with the message seen in the subject for this posting. What is really strange is that there is no problem running Ant 1.5 from command line on the exact same build.xml. It only has a problem when run through Eclipse. Has anyone seen this? I've spent a good amount of time looking for this error in various newsgroups. The error is out there, but most every posting seen has been an initial posting with no reply. The javadoc target is:
but this probably does not matter because Ant 1.5 from commandline processes this target without complaint.
Can you get some more info from your .log - file in the .metadata directory?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Nov 22, 2008
Ilja, Oddly, no -- these events are not logged. I tried shutting down and restarting Eclipse in hopes that the log had not been flushed. Repeated attempts have failed to get anything related to this issue in the .log file. I have, for the time being, opted to use Ant 1.5 from commandline. This has been fine and everything is working. I'll run this issue past a guy at work who knows lots about Eclipse and post his insight here.
Originally posted by Uwe Kubosch: How do I add javadoc.exe to the PATH of the ant script in Eclipse without using a script file?
It's not an issue with the ant path, but a problem with the system path. i.e. can you type 'javadoc' at the command line and have the system resolve it? This is effectively what ant tries to do. If it fails for you, it will fail for ant! Note that once you get it fixed for yourself, you need to restart eclipse/wsad for it to pick up the new path.
"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.
If you are using ant integrated into Intellij Idea (I am using v3), you may need to change the build file properties, and under "execution", select "Run under custom JDK", as your system default JRE/JDK may not have javadoc.exe. Obviously then you select a JDK which _does_ have javadoc. [ July 30, 2004: Message edited by: dan skal ]
I know this is an old topic, but i had this problem too. Except I had one machine that it would work on and another that it wouldnt.
Eventually i found that the problem wasnt the classpath but the system path, if you make sure that the jdk/bin folder is in the system path then ANT will find the javadoc in eclipse (requires a restart).
Hope this helps.
Pinky & the Brain <br />---------------------<br />Pinky: What are we going to do tonight Brain?<br /> <br />Brain: The same thing we do every night Pinky, try to program Hello World.
Another possible reason for the problem is the command line is too long. We were using individual class names in our class path (turning a class path ref in ANT into a class path and then passing it in). We have hundreds of classes. We did the obvious solution, which was to put a jar file containing the class files into the class path.
This was working on one computer (win XP with cmd) but not working on others (win XP with cmd, win 2k with cmd, both computers via ssh).