I'm working on a multi-module project that is run on IBM WAS 6 server. We used to use a plugin made in-house for deploying to WAS back when we used maven 2.2.1 for the builds, but I encountered some problems with transitive dependencies when upgrading to maven 3, and found switching to org.codehaus.mojo:was6-maven-plugin easier than trying to get the in-house plugin to work. Now I have noticed that when I generate the javadocs (with javadoc:aggregate from the multiproject directory), I end up having javadocs for not only the classes written and maintained by ourselves, but also for the classes generated by the deployment plugin. They just needlessly clutter up the class list, nobody here is really interested in the javadocs for generated classes anyway.
was6-maven-plugin generates the deployment sources in target/generated-sources under each subproject directory and they seem to be included in the -sourcepath option for the javadoc generation, is there a way to leave them out and only generate from the src directory of each project? Or to at least skip every source file beginning with "EJS"? The only helpful option I found in the javadoc plugin documentation at http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html was excludePackageNames, but most of the generated classes use the same package names as our own classes. I have tried the -Dwas6.skip command line parameter, but it didn't help. (I don't subscribe to the list, so if you reply also directly to my address, it'll be easier for me to reply if further information is needed.)
