On Mar 27, 2007, at 9:47 AM, Daniel Kulp wrote:
It makes dependency management MUCH easier. It also specifically
prevents a lot of "bad practices". By having each in a separate
module, it's completley impossible to produce a bunch of spegetti code
with circular references and such. Every single time I've looked
at a
project that tried to build things into one module, the code has
been a
disaster.
You're mixing up compile time with build time. By all means, have as
many source modules as you want to maintain whatever good design
practice you want to. As a user, this is irrelevant to me. There
should not be a 1-1 mapping between source modules and jar files. The
multiple modules is to allow you (the developers) to scale the
project and grow it in a sensible manner over time, which is great.
As an end user, all I want is to use cxf.
There are three categories of folks I need to keep in mind:
1) CXF developers - basically, the folks on cxf-dev that are in the
core
writing stuff.
2) Basic "end user" type folks. Most of these are happy with the
JAX-WS
specification or the other "basic" info we have up on the Wiki.
(Well,
the stuff that Dan is working on getting on the wiki. More work is
needed on this front.)
Yes, and being in that category, I don't want to add 8 cxf jars. It's
an irritating barrier to adoption. Does a single user on this list
think this is a good idea? Please speak up if you *want* dozens of jars.
3) Advanced developers - these are the folks that are writing
interceptors, writing new bindings/transports, etc.... For these
folks, the javadocs in "api" are the important things.
You honestly think that these developers won't know that a package
called 'internal' or 'impl' is not public, even if that's documented?
In the 3 groups above, there are sometimes conflicting needs. Right
now it looks like the people most catered to in terms of packaging
are the first group, which seems a bit...odd.
