The issue turns out to be that the 'package' statement in the class was wrong! I have no idea why the compiler, and checkstyle, and PMD, all allowed this, but javadoc was the only canary to chirp.
On Thu, Aug 18, 2011 at 10:18 AM, Anders Hammar <[email protected]> wrote: > Does it work with command line javadoc tool? > > /Anders (mobile) > Den 18 aug 2011 16.05 skrev "Benson Margulies" <[email protected]>: >> There is exactly one java source file, for a public class, in the >> package cited below. There are no exclusions set up. Anyone have a >> clue? >> >> INFO] [javadoc:javadoc {execution: default-cli}] >> [INFO] >> 1 error >> 1 warning >> [INFO] > ------------------------------------------------------------------------ >> [ERROR] BUILD ERROR >> [INFO] > ------------------------------------------------------------------------ >> [INFO] An error has occurred in JavaDocs report generation: >> Exit code: 1 - javadoc: warning - No source files for package >> com.basistech.rosette.rex.hadoop.sample >> javadoc: error - No public or protected classes found to document. >> >> Command line was: >> > /Library/Java/JavaVirtualMachines/1.6.0_26-b03-384.jdk/Contents/Home/bin/javadoc >> @options @packages >> >> Refer to the generated Javadoc files in >> '/Users/benson/x/tej/hadoopdemo/target/site/apidocs' dir. >> >> --------------------------------------------------------------------- >> 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]
