Hi,

  We're generating some source into target/generate, and we'd like to run
javadoc on it.  Currently (RC1) javadoc is only run on the source in
pom.build.sourceDirectory.  Reading through the mailing list, I see that
after this thread:

http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&m
sgId=807588

  the javadoc plugin was changed to use the maven.compile.src.set variable
instead, and users could append additional directories to it to generate
javadoc for those directories.  However, this was changed between versions
1.15 and 1.16 of the javadoc plugin.jelly:

http://cvs.apache.org/viewcvs.cgi/maven-plugins/javadoc/plugin.jelly?r1=text
&tr1=1.15&r2=text&tr2=1.16&diff_format=u

  I think the right thing would be to have the javadoc plugin iterate across
the directories in maven.compile.src.set, generating a fileset tag for each
directory with appropriate exclusions.  Does this sound right?
Unfortunately, my attempts to do this the <j:forEach> tag brought nothing
but heartbreak and psoriasis.

  So, my questions:
 - should the javadoc plugin be using maven.compile.src.set rather than
pom.build.sourceDirectory?
 - if not, how should non-src/java directories have their javadoc created?
 - if so, can someone point me at some (any!) documentation for the forEach
tag?

  Many thanks... :)

Denis

Reply via email to