On 9/12/07, Prashant Reddy <[EMAIL PROTECTED]> wrote: > > On Wed, 2007-09-12 at 14:37 +0100, Peter Reilly wrote: > > > 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> > > I was thinking may be Javadoc task can pick up the package-info.java > while it is processing the input filesets. I am not familiar with > Javadoc task's code, may be this not possible. The Javadoc task does not have code to process the fileset itself, it used org.apache.tools.ant.DirectoryScanner and others.
> > > 2) package-info.java is used by other things than javadoc. > > Really, Like what other things ? JAXB > I read that javadoc tool starting JDK > 1.5 chose the name package-info.java precisely because it was invalid > and couldn't have existed before. It is used for package level annotations. The annotations can be compile time or run time. JAXB uses run-time annotations to specify the mapping of package to URI, and other package level mapping defaults for the classes in the package. Peter > > Thank you for taking time to respond. > > -Prashant > > > > > > > > Do ANT-experts think including the package-info.java where ever its > > > found too much magic ? > > yes > > > > --------------------------------------------------------------------- > 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]
