Hi, I had sent the email below asking for some information about modifying the maven javadoc plugin to properly support the maven.compile.src.set. I've generated a patch that seems to do the right thing: it's attached below. Comments quite welcome.
I looked at making a patch against 1.5, but the fileset generation was pushed into the check-needed tag between versions 1.3 and 1.4, and I'm unclear on how to preserve the function of the filescanner across multiple filesets. (refids based on the dir name maybe?) Plus it's nearly 1:30am and I wanna go to bed. :) Hope this is useful. Denis On Thu, 2004-05-13 at 20:42, [EMAIL PROTECTED] wrote: > "Denis McLaughlin" <[EMAIL PROTECTED]> wrote on 14/05/2004 > 09:45:58 AM: > > > > > 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 > > Yep, it looks like my addition of sourceModifications removed the > src.set > usage. > > > 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? > > Yes. > > > 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? > Yes. > > > - 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? > > http://jakarta.apache.org/commons/jelly/tags.html > > I'm happy to help with this if you get stuck or just want another pair > of > eyes on it, as once it's done for javadoc, we can apply it across the > other plugins too. > -- > dIon Gillard, Multitask Consulting > > > --------------------------------------------------------------------- > 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]
