mail at ulerch.net
Do Mär 13 20:50:31 CET 2008
Yes, I agree that double the information wasn't a good idea. So doxygen
is fine with me.
And I really think that a nightly build is a MUST! But how do we get
there? Who could manage that? Is there anybody else out there?
I don't know what the infrastructure looks like, but I guess there
should be a little bit of machine resource left for this little task. If
I had the account information I would do it, though I'm not really an
expert in such things - in my former job I used to have my "ants" :)
Am Donnerstag, den 13.03.2008, 16:54 +0100 schrieb Enrico Schnepel:
> > (1) javadoc compatible (no compromise there!)
> and it knows some more javadoc tags as javadoc itself does
> you could document groups of functions for example.
> > (2) integrated in eclipse
> I am prefering the command line way...
> what about an automated checkout and a doxygen build on a nighly basis.
> the build log could be also send to the dev-list if the where errors in the
> build. - continious integration! and... if we have some unit tests these may
> run too.
> > (3) easy to set up
> using a wizard - it is
> > So, why don't we use both of them, javadoc and doxygen? It's not that
> > much work, at least with javadoc. And if we see, after some time, that
> > there is only one documentation used, we could easily skip the other
> > then.
> this would double the information and it would make no sense to me if i would
> see two documentation links on the website.
> > In my opinion it is important that there's a documentation in the code
> > at all, and that it is done in a widely used and accepted
> > standard/style. Anything that helps as a motivation to do this is
> > welcome.
> deepamehta-devel mailing list
> deepamehta-devel at lists.berlios.de
Mehr Informationen über die Mailingliste devel