Sounds like a great idea, I remember thinking of something along these lines a while back ... but only as a documentation exercise. Adding a url to the jar download would be really nice for our users.
As a secondary idea, how hard would it be to include the dependency set during javadoc creation? does anyone have any ideas how this could be performed automatically (was thinking it could be done using the project.xml
file ... generqating / augmenting the package.html files). Just an idea to throw out ... probably too much work thought.
DZ
On 1/4/06, Martin Desruisseaux <[EMAIL PROTECTED]> wrote:
We currently have the following javadoc tag in every .java files (in
theory):
@version $Id$
where $Id$ is a Subversion keyword. I would like to add the following
javadoc tag in every .java file too:
@source $URL$
where $URL$ is an other Subversion keyword.
All source file in the whole Geotools project would be affected, but
this addition need to be done only once. After that, $URL$ is managed by
Subversion in the same way than $Id$
Why I would like that: it would allow us to create a small javadoc
taglet that automatically put, in every javadoc HTML pages, the module
name and the jar file where the documented class can been found.
Can I add "@source $URL$" in every file? (I would use some automatic
script that add just this line and change nothing else).
Martin.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
