The reason we need to do it is that this a closed-source, proprietary
product and we'd prefer not to give away all of the internals of the
system. It's not practical to remove all classes we don't want to
document from the "public" packages. The other reason we don't want to
document some classes is that they will change in the future, and we
only want people writing to the interfaces that are stable. You can
guarantee that if we document it, then people will use it, and then
we've got a backward compatibility problem for future releases.
I found the solution to the problem: keep everything in Ant, and use the
Ant Run plugin.
Wayne Fay wrote:
As always with things like this, I have to ask, why do want to only
run Javadoc on certain classes? Javadoc does not take *that* long to
run unless you have a TON of classes in your project, and Maven works
better with many small groups of classes than it does with one huge
project. Unless perhaps you're building up an API and only want to
produce docs on the public classes, but then I'd tell you to break
that into 2 (or more) Maven projects.
If this is really desired functionality and it is not offered by the
plugin, then an RFE in Jira may be called for.
Curious,
Wayne
On Sun, Oct 19, 2008 at 2:38 PM, Chris <[EMAIL PROTECTED]> wrote:
How do I get the javadoc plugin to do only certain classes?
The Ant javadoc task does it by letting you pass in a <fileset>. I can't
find the equivalent in Maven.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
