> > Anyway, I received a request to make xdoclet faster. I'm going to spend > > some time on it. More specifically I'll try to do some magic sourcefiles > > reduction so that javadoc doesn't load all classes by default but > > exactly those which at least one subtask needs to operate on. Any ideas? > > Tricks? Suggestions? Is anyone interested in doing a profiling? I'm > > trying to prepare it for a 1.1.2 release. > > > > Wouldn't it be better to put in the effort of making xjavadoc faster > instead? -Or would that be in addition? There is a lot of optimisations > that > can be done on xjavadoc. -And I presume the goal is still to ditch javadoc > in favour of xjavadoc.
It's in addition to xjavadoc and in fact it'll be beneficial to xjavadoc too. I'm trying to find a way to exclude javadoc/xjavadoc loading/parsing of a class if it's not needed to be parsed. Because the loading/parsing part is the performance bottleneck it'll indeed result in a very huge performance improvement. Of course xjavadoc will even give us much more control, so for example even if a class is included in sourcefiles list, we can postpone loading/parsing it to a later time when it's actually accessed. I'll try and if it's harder than I think I'll simply give up and put %100 time n xjavadoc and the lazy loading scheme I talked about above. I already started working on xjavadoc, stay tuned for my comments/codes ;-) Cheers, Ara. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
