On Mar 27, 2007, at 7:27 AM, Daniel Kulp wrote:
God no. I can see api and rt-core being combined. However, none
of the
other rt-* artifacts should be combined into it. All of those are
modular for a reason and should stay that way.
Why?
The separation of API and CORE is mostly to aid in javadoc generation.
If someone can find a easy way to generate javadocs for all the
stuff in
api, but not the stuff in core if they are combined, fine. However, I
don't consider a monser list of includes/excludes an "easy" way of
doing
it.
It's not easy for the developers, but who is the majority in cxf, its
developers or its users?
Remember, not everyone uses fancy IDE's and stuff. Javadoc of the
stuff
users/devs should be aware of is important.
Sure, so have your explicit list of javadoc packages to include/
exclude in your javadoc task.
Even if you DID have it all in one javadoc tree,you could easily just
drop in a package.html file in each 'internal' package with a
disclaimer saying it shouldn't be used. You can only suggest that,
you can't enforce it anyway. Have some faith in users.
