Hi Jason,
On Feb 15, 2007, at 3:55 PM, Jason van Zyl wrote:
Hi,
So that no one can accuse of resting on our laurels time to start
planning for 2.0.6. Not sure what the best way is to gather the
issues to work on but it would be nice to gather them in the next
week or so, and then work th
Hi Jason,
On Feb 16, 2007, at 7:36 PM, Jason van Zyl wrote:
On 16 Feb 07, at 4:43 PM 16 Feb 07, Eric Brown wrote:
Hi Jason,
On Feb 16, 2007, at 5:29 AM, Jason van Zyl wrote:
[snip]
Project with full test cases that can be easily absorbed will
be taken before anything else anything else
Hi Jason,
On Feb 16, 2007, at 5:27 AM, Jason van Zyl wrote:
On 16 Feb 07, at 1:12 AM 16 Feb 07, Eric Brown wrote:
My project's decided to continue using maven and patch it as
necessary to fix bugs in maven that we're no longer willing to
live with. I tried for an hour or two
Hi Jason,
On Feb 16, 2007, at 5:29 AM, Jason van Zyl wrote:
[snip]
Project with full test cases that can be easily absorbed will be
taken before anything else anything else. If these are for fixes
and you have unit tests that's great, or if you prefer to create
an integration test then to m
hought it would take
to actually fix them in the first place even if that meant we'd tell
our users to use our custom-build of maven.
Cheers,
Eric
-Original Message-----
From: Eric Brown [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 1:13 AM
To: Maven Developers List
Subjec
Hi Jason,
On Feb 15, 2007, at 3:55 PM, Jason van Zyl wrote:
Hi,
So that no one can accuse of resting on our laurels time to start
planning for 2.0.6. Not sure what the best way is to gather the
issues to work on but it would be nice to gather them in the next
week or so, and then work th
My project's decided to continue using maven and patch it as
necessary to fix bugs in maven that we're no longer willing to live
with. I tried for an hour or two to get my project to build under
2.1, but gave up and figured it was under too much active development
anyway. What is the time f
