On Jun 23, 2006, at 5:06 PM, Kevin Menard wrote:
The presence of an external contrib lib could be argued for, but
what I'm aiming to do is cut down on the amount of time to tie in
with whatever other frameworks. I also want something that is
fairly well supported and maintained.
I think the core of the issue is "supported and maintained" and not
the "same jar vs. a separate jar". We have these examples of
technologies that are somewhat tangential to Cayenne:
* Spring integration is not maintained cause nobody cares to maintain
it.
* WebObjects integration is fairly well maintained.
* DataViews is abandoned (inside Cayenne)
At the source level I would actually separate each integration piece
in its own Maven module (if only to have a clear separation of third-
party dependencies for the build build), and defer a decision of how
we assemble the release till we actually have those pieces written.
Andrus
