A wise old hermit known only as Clark Wright <[EMAIL PROTECTED]> once said:
> [ejbdoclet] WARNING: Some classes refer to other classes that were not > found among the sources or on the classpath. > [ejbdoclet] (Perhaps the referred class doesn't exist? Hasn't been > generated yet?) > [ejbdoclet] The referring classes do not import any fully qualified > classes matching these classes. > [ejbdoclet] Since at least one package is imported, it is impossible > for xjavadoc to figure out > [ejbdoclet] what package the referred classes belong to. The classes > are: ... > It appears that in 1.1 XDoclet correctly figured out a classes package > and/or propagated the includes from the EJB to the interfaces, and now > in 1.2 it completely punts on that process. > > Any comments or suggestions welcome and desperatly needed. One of the big changes in 1.2 is that you should now either use fully qualified class names, or import the classes individually (not with "import my.ejb.interfaces.*;"), so that xjavadoc doesn't have to try (and often fail) to guess where they will be. If you don't, you get this message. It does tell you which ones it can't find, though, so you have some clue as to where you need to add the imports. Andrew. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
