Kim, questions (c) and (d) are good ones, making me wonder whether
there is a list of to-do items somewhere that we can transfer into
Qpid JIRA, assuming we get that set up soon? That way the group would
get a much better idea of how much work there is to do, so we can
better prioritize it.
--steve
On Sep 8, 2006, at 9:28 AM, Kim van der Riet wrote:
While the advantages of Maven seem clear, the question becomes:
a) How much effort will it take to implement Maven at this stage?
b) What is the risk of disruption to the development process if there
are hiccups?
If the answer to these questions is little effort, little risk,
then it
seems to make sense to go ahead and make the change - if someone is
willing to do so. If the change involves significant effort and/or
risk
of disruption, then I would also ask the following:
c) Does Maven bring any immediate advantages to the project that could
help it along?
d) Is the effort spent implementing Maven better spent elsewhere on
the
project right now? There are still many holes and fixes that are
urgently needed, and would it not be better at this juncture to rather
concentrate on the "nuts and bolts" issues?
e) Is it wise to introduce another major system change at the same
time
that we switch our source from 108 to Apache?
Given the general support for Maven and the advantages it brings, this
is not a question of "if" but of "when". Lets consider whether this is
in fact the best moment for such a change.
Kim
On Fri, 2006-09-08 at 08:59 -0400, Carl Trieloff wrote:
Steve,
"You said Maven doesn't help us at this stage. In response gave 10
good
reasons why it does." - all I wanted
was a window do get the code move done, thus should have said, adding
maven now does not help ME in the
code move. We all know the merits of maven. I am appreciative that
you
are willing to work out what the
project will look like.
Carl.
