> IMHO this a big problem with xjavadoc, and we have to kill it completely. > I find it useful to put the generated src dir in the fileset of ejbdoclet > so > that the "qualify" will work. But this does not work at the first build. > So I build twice. > I don't think your trick is better because some IDEs replace 10 single > import's into 1 package import automatically so the problem will come > back. > Users will complain,... > Not good. > Why not WARN the user when a class can not be qualified. Aslak : what > does > happen if a class can not be qualified ? I think it is considerred as > being > with no package. > Or better: restart a second generation when a qualify failed. > Ideas ?
Well, isn't it what javadoc.exe does and we hate? :-) We should come up with good patterns/guidelines for it. I'm eager to listen to good ideas.... Ara. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
