Re: [aspectwerkz-dev] aw doc

Quote [Alexandre Vasseur]:

> ha i see, u wanted to virtually produce a set of source file with qdox
> that contains the original javadoc + some custom doclet for the
> purpose like "@AdvisedBy systemId/aspectFQN/advice : <inflated
> pointcut expression>

yes, this is my idea (for the moment, at least)

> etc
> mhh, i am wondering which one is the easiest to do

yep, me too. i will put more thinking/analysis into this.

> 
> side node: Qdox had some limitation about parsing sources with the
> assert keyword, and don't know about java 5 syntax yet.
> 

i hope that QDox guys are working on this. I think we can ask on the mailing list what are their 
goals and roadmap. a not so optimal solution would be to patch the QDox with the needed infos (I 
already have some experience with QDox ;-) ).

./the_mindstorm

PS: I am late with the AspectWerkzC task as I am facing some classloading problems. for the moment I 
am trying to figure out a solution.



> alex
> 
> 
> On Sun, 10 Oct 2004 22:20:54 +0300, the_mindstorm
> <[email protected]> wrote:
>> The solution Alex proposed looks very interesting.
>> The solution I've imagined (trying to remember the previous thread on the subject) would look like:
>> 1. scan the sources and create a QDox model representation
>> 2. make the offline compiler generate some events on aop events (poincuts, aspects, etc)
>> 3. use the above events to complete QDox model with aop-ish info
>> 4. use javadoc with custom doclet to generate docs
>> 
>> 
>> ./the_mindstorm
>>
>