On 9/12/07, Prashant Reddy <[EMAIL PROTECTED]> wrote: > Hello ANT Users, > > I have a lot of files from which javadoc needs to be generated. > > Not all java files from a package need to be published in javadoc. > > To enable this i use a number of <fileset>s that provide input to > javadoc task. > > Something like : > > <javadoc> > <fileset dir="module1/src"> > <include name="A1.java"/> > <include name="B1.java"/> > <include name="C1.java"/> > </fileset> > <fileset dir="module2/src"> > <include name="A2.java"/> > <include name="B2.java"/> > <include name="C2.java"/> > </fileset> > .... //More filesets > > </javadoc> > > However to my surprise package-info.java which i placed in packages is > not included as input to javadoc task. I had to modify the fileset > include to put in package-info.java > > <fileset dir="module1/src"> > <include name="**/package-info.java"/> > > And i had to do this for every file set, violating "DRY". > > Shouldn't javadoc task pick this artifact (package-info.java) given that > this file is meant only for the javadoc tool ? Why should the user have > to explicitly include it ? 1) the fileset is not only used in <javadoc> 2) package-info.java is used by other things than javadoc.
> > Do ANT-experts think including the package-info.java where ever its > found too much magic ? yes Peter > > Thank you > -Prashant > > > --------------------------------------------------------------------- > 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]
