Vikas, I have exactly this right now. I have 26 projects each with its
own javadoc generated using looping through each one of them. However,
the projects are defined using logical functionality, not package
structure, so subpackages at the same level end up in different javadoc
hierarchies. To get an overview of the top-level packages is very
difficult then.
Also, I can't get an overview page of all of the subprojects after they
have been produced (limitation of the javadoc executable).
That is why I am still looping but only to get the src/classpath
directories for the subprojects which I am accumulating in the
${javadoc.src.path} and ${javadoc.class.path} properties.
Now I want to feed those two into the <javadoc/> task, not to try to use
exec. I was not able to do it with nested elements, dirsets, patternsets
etc. I would appreciate your further help with this.
Thanks,
--
Svetlin
> -----Original Message-----
> From: Vikas Phonsa [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 13, 2003 5:50 PM
> To: 'Ant Users List'
> Subject: RE: javadoc of multiple sub-projects
>
>
> Hi Svetlin,
>
> If you are trying to build javadocs for multiple projects (
> subprojects or
> not) then you should consider for-each task of ant-contrib.
>
> I achieved this functionality by using the javadoc task in
> for-each. It would be like a for loop in java would loop
> through all your projects and build docs.
>
> I had another twist to it, I had to build docs from my CVS
> repository and that's how I did it.
>
> I can send you more details if you need.
>
> Thanks
>
> Vikas
>
> -----Original Message-----
> From: Svetlin Stanchev [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 13, 2003 4:49 AM
> To: Ant Users List
> Subject: javadoc of multiple sub-projects
>
> Javadoc cannot meaningfully "incrementally" build docs of an
> entire project group based on already existing docs of subprojects.
>
> That is why I am attempting to feed to it a path consisting
> of all source/class subdirectories of all individual
> projects. I was able to make it work for one subproject only,
> and only using a fileset. So I am surely doing smth
> fundamentally wrong.
>
> For instance this does not work:
>
> <echo> Src path: ${javadoc.src.path}</echo>
> <echo> Class path: ${javadoc.class.path}</echo>
> <javadoc
> destdir="${javadoc.dir}"
> author="true"
> use="yes"
> version="yes"
> windowtitle="My Documentation"
> private="yes"
> linksource="yes"
> breakiterator="yes"
> verbose="no"
> failonerror="no"
> maxmemory="384m"
> useexternalfile="yes">
> <sourcepath>
> <pathelement path="{javadoc.src.path}"/>
> </sourcepath>
> <classpath>
> <pathelement path="${javadoc.class.path}"/>
> <pathelement path="${mountpoint.libs}"/>
> </classpath>
> </javadoc>
>
> It fails with:
> BUILD FAILED
> D:\cleanstart\buildroot\masterbuild\build.xml:199: No source
> files and no packag es have been specified.
>
> Although any directory in the list correctly points to the source root
> hierarchy:
>
> [echo] Src path:
> D:\cleanstart\buildroot/masterbuild/projects/ctrl/src;D:\
> cleanstart\buildroot/masterbuild/projects/clients/src;D:\clean
> start\buil
> droot/ma
> sterbuild/projects/TexCoreCommon/src;
> [echo] Class path:
> D:\cleanstart\buildroot/masterbuild/projects/ctrl/build
> /classes;D:\cleanstart\buildroot/masterbuild/projects/clients/
> build/clas
> ses;D:\c
> leanstart\buildroot/masterbuild/projects/TexCoreCommon/build/classes;
>
> Some of the above projects do not have Java source, but this
> should not lead to a fail, I think.
>
> Any help appreciated,
> --
> Svetlin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
