Explicitly specify classes but keep package frame...

Question

I'm trying to generate the Javadoc for a set of classes. Unfortunately those classes belong to the same package as some other classes on the classpath (essentially core and extensions but not separately packaged).
When I try to Javadoc the extension source it generates documentation for all the core source too (contained in a JAR on the classpath). This documentation is, of course, lacking all relevant commentary since it comes from the compiled code rather than the source.
I know I can't exclude the core files from the documentation step.
I have tried explicitly naming all the classes that I want documented but this results in the loss of the package frame (top-left frame). This is inconsistent with the other documentation that's been generated and is, needless to say, a real pain!
The only thing I can think of is to copy all relevant core documentation over the top of the new core documentation to avoid having loads of empty class docs. This is likely to become a bit of a maintenance nightmare.
If anyone's hit upon similar issues or got any advice then I'd like to hear it.
Many thanks,
K.

Answer 1

Doug,
Here's part of the script that's used to build the project and its Javadocs (the package names have been changed to protect the guilty):
set CLASSPATH=../lib/core-1_0.jar;../lib/servlet.jar
set JAVA_PACKAGES=com.blah.contentmanagement com.blah.database
set PACKAGE_NAME=content-management-1_0
cd src
javadoc -package -sourcepath . -stylesheetfile %STYLESHEET% -windowtitle %PACKAGE_NAME% -d ..\doc\api %JAVA_PACKAGES%The project being built is for content management, hence the desire to Javadoc the contentmanagement package. However, another package, the database package, has some content management classes in it. Their Javadoc commentary is being generated alright.
The problem arises because the core packages in the core-1_0 JAR file also contain core database classes, also in the com.blah.database package.
The Javadoc command issued above results in Javadocs being generated for all com.blah.database classes, including those in the core-1_0.jar file. Obviously those present in the JAR are being generated with empty commentary.
As mentioned previously, explicitly specifying the classes removes the package frame (in JDK 1.3 anyway) and so isn't an option. It would also represent a maintenance problem going forward.
I realise that the package structure being employed in this project is unusual; I'm trying to split legacy code to separate what can be reused!
Hope this provides sufficient information,
K.