Is there a way to generate a Javadoc directly from an SVN repository? (or do I need to actually check out the code?)
+3
A:
You can do a svn export to a temporary directory, generate the javadoc, then delete the temporary directory. Do this in a script. Then it feels like you did it directly.
Dave
2009-12-11 18:25:28
I'd considered that, but I'd still have to generate a copy of the code -- it seems like one ought to be able to do this directly...
Mark E
2009-12-11 18:26:35
If you look at the repository on disk, you'll see that there is really nothing you understand as your code in there, so I don't see how it would be possible unless SVN specifically added support to do this.
Dave
2009-12-11 18:48:45
+2
A:
The idea is to never interfere with the repository. Thats why you have to create a working copy to make any modifications. If you use continuous integration tools like Continuum then you can have JavaDocs generated automatically for you. I think (correct me if I'm wrong) that the continuous integration servers check out your code and perform these taks for you so you do not have to perform them yourself.
Vincent Ramdhanie
2009-12-11 18:36:12
I'm pretty sure you're right about it checking out the code (or exporting, I haven't checked). I know that's what Hudson does.
R. Bemrose
2009-12-11 18:37:03
A:
If the Subversion repository is accessible via HTTP, then you might be able to mount it as a WebDAV filesystem, depending on OS support...
but really, it's simpler to just export the sources, run Javadoc, then delete the export as Dave suggests. If you're going to be running Javadoc multiple times then check out the sources once and just update before every run (to save time).
ZoogieZork
2009-12-11 18:47:53