On Sep 12, 2006, at 3:09 AM, [EMAIL PROTECTED] wrote:
We certianly have awareness of tasks that need to be prioritised
for the
jms client. As soon as there's a project tracker/jira on Apache
that we
can use we can start there.
I think getting JIRA up as soon as possible could help in a number of
areas. I suspect that those of you who have been working on the code
for awhile could quickly add a bunch of to-do tasks to JIRA.
On the maven front, I just want to (sorry but feel very strongly)
state
that any work on the build system must be isolated until complete &
tested
on all platforms. I cannot go back through build related pain :-)
I have no issue with that whatsoever, and is in fact part of the
reason I talked in another email thread about creating a branch, so
that we can all test the maven stuff on a variety of platforms before
deciding if and when to move to it. Having a working build system is
paramount.
However, what does "all platforms" mean? Are the platforms that must
be supported documented somewhere?
thanks,
--steve
Regards,
Marnie
Steve Vinoski <[EMAIL PROTECTED]>
08/09/2006 21:53
Please respond to qpid-dev
To: [email protected]
cc:
Subject: Re: maven
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.
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
