Community
Participate
Working Groups
Build ID: M20080221-1800 Steps To Reproduce: 1.create a Aspect: aspect A{} 2.call ajdoc with -protected or -public More information: Ajdoc seems to generate a java file for this aspect that is in the form. class A{} When ajdoc calls javadoc with this file, nothing is generated because unspecified visibility defaults to package. My understanding is that an Aspect can only have the modifiers public, abstract or final, therefore the documentation for this aspect should be generated. If an aspect has an unspecified visibility should the signature generator append public to it?
It seems that declares also don't show up if -protected or -public is set. I looked at the accessibility for declares and it's set to package for all declares. The decorator checks for proper visibility when generating the declare summary and detail and skips over the declares because of this. I'm not sure how handle this one. One way would be to set the accessibility to public for all declares. Another is to set the accessibility to that of the class that is being declared on.
havent had time to think about this properly, scheduling for 1.6.3
i still haven't decided what to do with this - how urgent is it for you? My first thought is that I don't mind the signature generator prepending public for the aspect decl. On the second issue, can the decorator not just be more aware of declare constructs and always include them?
(In reply to comment #3) > i still haven't decided what to do with this - how urgent is it for you? My > first thought is that I don't mind the signature generator prepending public > for the aspect decl. On the second issue, can the decorator not just be more > aware of declare constructs and always include them? My original thoughts on appending the public tag was if there was ever a reason to have a aspect not be visible in the documentation. I can't really find a case in which an aspect would have such a visibility so I'll go ahead and append public to the code if it doesn't exist. On the second issue my confusion was what to do when a class has a visibility of package. Should the aspect show in it's summary that it declares on a package class. An example of this is if a public class A extends a package class B. When javadoc -public is run on these files the generated html doesn't show that A extends B. If I then use an aspect to make A extend B and I went ahead and included all the declare summaries then I would be revealing that A extends B in the Aspect documentation. This seems to have the opposite behavior of javadoc.
unsetting the target field which is currently set for something already released
