ashkelon provides a tool called "apixml" that assists you in producing ashkelon API descriptors.

For a given API, search its javadocs directory for a file named package-list. This file is a sort of signature that javadoc leaves behind after processing an API.

Feed apixml this file and it will produce an almost completed xml descriptor file for you. In the example session below, I process junit's package-list through apixml. The xml output is produced by apixml. Now simply specify the missing pieces: API name, description, publisher, url, and version control system information.

eitan@ubuntu:~/devel/junit/javadoc$ apixml package-list
               

<?xml version="1.0" encoding="UTF-8"?>
<api>
   <name/>
   <summarydescription/>
   <description/>
   <publisher/>
   <download_url/>
   <release_date>2006-02-03T20:21:45.151</release_date>
   <version/>
   <packages>
      <package>junit.extensions</package>
      <package>junit.framework</package>
   </packages>
   <repository>
      <type>cvs</type>
      <url>:pserver:anonymous@cvs.sourceforge.net:/cvsroot/[projectname]</url>
      <modulename>[projectname]</modulename>
      <tagname/>
      <sourcepath>src/java</sourcepath>
   </repository>
</api>
eitan@ubuntu:~/devel/junit/javadoc$
</screen>