I've been extensively modifying jdt.core plugin, including the grammar itself. It has come to a point where I need to be able to present the users with an ability to use javadoc tool. The trouble is that javadoc is an outside tool that is oblivious to the newly introduced grammar changes, and the whole process of generating the documentation fails. Such a thing happens due to the fact that javadoc uses the standard javac compiler instead of the modified grammar inside jdt.core. The question is, can you recommend an open-source javadoc-like plugin for eclipse, and is there even such a thing?

On 01.07.2011 12:31, Milan Vidakovic wrote:
> Greetings.
>
> I've been extensively modifying jdt.core plugin, including the grammar
> itself. It has come to a point where I need to be able to present the
> users with an ability to use javadoc tool. The trouble is that javadoc
> is an outside tool that is oblivious to the newly introduced grammar
> changes, and the whole process of generating the documentation fails.
> Such a thing happens due to the fact that javadoc uses the standard
> javac compiler instead of the modified grammar inside jdt.core. The
> question is, can you recommend an open-source javadoc-like plugin for
> eclipse, and is there even such a thing?
I don't know of any but maybe you can write your own doclet that then
interacts with JDT Core.

>>I don't know of any but maybe you can write your own doclet that then
>>interacts with JDT Core.
>>
>>Dani
Hi Dani,

I thought javadoc doclets only helped with the "look&feel" portion of the javadoc experience. When standard javadoc bumps into a new custom keyword, or an operator overloading feature, it pops-out a compile error. If a simple doclet could make javadoc look past that, it would be a life-saver to me. Could you, please, elaborate on your proposition just a little bit more, so I could start looking into it, since I've been pondering a thought of making a javadoc plugin for eclipse from scratch.

On 12.07.2011 19:10, Milan Vidakovic wrote:
>>> I don't know of any but maybe you can write your own doclet that
>>> then interacts with JDT Core.
>>>
>>> Dani
> Hi Dani,
>
> I thought javadoc doclets only helped with the "look&feel" portion of
> the javadoc experience. When standard javadoc bumps into a new custom
> keyword, or an operator overloading feature, it pops-out a compile
> error. If a simple doclet could make javadoc look past that, it would
> be a life-saver to me. Could you, please, elaborate on your
> proposition just a little bit more,
It was just a hint. I would also have to dig deeper to give more details.

Dani
> so I could start looking into it, since I've been pondering a thought
> of making a javadoc plugin for eclipse from scratch.
>
> Thank you
> Milan