On Wed, 19 Apr 2006, J-F Daune wrote: > > That 'works', in the sense that XDoclet now tries to generate something. > > But I unfortunately got other exceptions. > > What strikes me, is that the example is taken from a project using M1, > to evaluate impact of switching to M2. > With M1, it works without the 'implements', and I am reluctant changing > my source code for M2. > > Could it be a classpath issue?
I've looked at the code for xjavadoc, and any dependencies are not used. Each source class is represented by an XClass instance, which knows about implementing interfaces and such. The dependency is represented by an UnknownClass, and does not contain any information. A big shortcoming of XDoclet, since this information can easily be extracted using reflection. Nothing I can do, I'm sorry. I really don't know why/how that worked in Maven 1 - maybe it used an old version of XDoclet that worked differently. Maybe the XDoclet2 plugin is something to look at? -- Kenney > > > J-F > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
