On 1/2/07, Bernd Fondermann <[EMAIL PROTECTED]> wrote:
On 12/2/07, Norman Maurer <[EMAIL PROTECTED]> wrote:
> Wel my idea why i want to move it into a subproject was that maybe some
> developer whould find it very usefull to just use a framework for
> getting a bayesian filter integrate with their software. I think most of
> developer don't need a full mailserver like james. Thats only my point
> of view..
ok. so factor it out that it starts standing on its own feet while
being integrated with Server at the same time.
if it starts to grow out of the Server, let's shift into a subproject.
that would be a more evolutionary process.
what is the size of the codebase we are talking about?
I think it's helpful to disguish between code indepedence and project project.
I'm fine with separating the code to make it more independent and
possibly even a separate ant build task or its own build.xml. A
subproject however suggests separate release cycles and a lot of other
independence that IMHO is not yet justified.
As an example of how this is done, there's a JDBC lucene store within
the compass framework
(http://www.theserverside.com/news/thread.tss?thread_id=38478). The
code is completely separate so as an outside user I can use the JDBC
lucene store without all the compass framework stuff, but they release
everything at the same time and keep it in the same source tree.
--
Serge Knystautas
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
