There are 2 configurations in the POM for building Javadocs: one in the parent uimaj POM and one in the uimaj-distr POM.

The thinking behind this was that the one in the uimaj-distr POM would run as part of the assembly process, and build Javadocs for the binary distribution, consisting of the external APIs. The one in the parent would run when doing a mvn site plugin, it includes more "internal" packages in the set of Javadocs being produced.

The idea is that we could post the internal ones for developers to use/access on our web site. I don't think we're doing this, now, however. We do post the ones generated for the release, I think, instead. Can anyone confirm this?

What should we do going forward? I see somewhat limited value to doing another set of developer javadocs, given that the developers have the source to work with.

-Marshall

Reply via email to