On Tue, Sep 27, 2011 at 8:39 AM, Michael Bedward
<[email protected]> wrote:
> When the taglet is processed during javadoc creation there must be a
> way of getting at the source path: e.g. from the taglet API or via
> maven or even by reflection we have to. In other words, let's try
> dispensing with the requirements for the path to be in the source file
> at all. The only reason I've been doing that is because that's how the
> taglet was written originally and I've been too lazy to think of
> better ways.  As well as side-stepping the formatting problem this
> would also deal with git being too dumb to work with svn:keywords.

There might be no way to do what you want using the standard doclet
api, which is pretty
limited, but in the past I've worked on umlgraph, a tool that
generates class diagrams out
of java code, and that has a custom doclet embedding said diagrams in
the javadoc output.

Instead of being a taglet the tool wraps the standard javadoc generator though
Might be worth checking out, it's a more heavy weight approach (might
be way heavier
than you are interested in) but it also gives you a lot of liberty in
what the output
will look like.

Cheers
Andrea

-- 
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy

phone: +39 0584 962313
fax:      +39 0584 962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-------------------------------------------------------

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to