)
-Original Message-
From: Andrew Williams [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 1:06 PM
To: Maven Developers List
Subject: Re: Working toward 2.0.6
This is now fixed in the latest plexus, which is being used in 2.1-
SNAPSHOT.
We are currently trying to figure if it is feasible to
Subject: Re: Working toward 2.0.6
This is now fixed in the latest plexus, which is being used in 2.1-
SNAPSHOT.
We are currently trying to figure if it is feasible to update the 2.0.x
branch at this time.
Andy
On 16 Feb 2007, at 16:30, Brian E. Fox wrote:
> Since this is a plexus issue, I might
struggling with PLX-287. I haven't been able to produce a test set
because it seems to only occur in very large complicated build.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 15, 2007 6:55 PM
To: Maven Developers List
Subject: Working t
On 22 Feb 07, at 4:34 PM 22 Feb 07, Eric Brown wrote:
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
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
The current 1577 sandbox patch was done on the trunk -- I am working on
getting both the trunk updates and the 1577 updates applied to this sandbox
(through Mike).
Jason -- I assume you still want this done on the trunk (not 2.0.6)
correct? (It would be easier in 2.0.6 just in case you could go
On 2/17/07, Eric Brown <[EMAIL PROTECTED]> wrote:
It took me a bit to figure out the example(s). I went to the maven
wiki to add a page about writing tests, but I don't have write
permission.
Try this one instead:
http://docs.codehaus.org/display/MAVENUSER
--
Wendy
---
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. If
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. If these are for fixes
and you have unit tests that's great, o
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
rsday, February 15, 2007 6:55 PM
To: Maven Developers List
Subject: Working toward 2.0.6
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
Please let me know where it is too.
Mike Perham wrote:
I was hoping I wouldn't have to "remind" you with a baseball bat this
time. :-)
We've found two issues with our patch in the two weeks we've been
using Maven with it applied locally. We'll have an updated sandbox
for you to review shortl
On 16 Feb 07, at 2:10 AM 16 Feb 07, Eric Brown wrote:
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
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
I was hoping I wouldn't have to "remind" you with a baseball bat this time. :-)
We've found two issues with our patch in the two weeks we've been
using Maven with it applied locally. We'll have an updated sandbox
for you to review shortly.
mike
On 2/15/07, Jason van Zyl <[EMAIL PROTECTED]> wr
Let's try the voting + priority thing (though noting that many will
not be appropriate for 2.0.6). ie, take care of the things important
to people, and the ones that have a critical impact.
If we form the roadmap from that, we an then start taking
suggestions from people on where that does
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 the next three weeks to resolve them and do
another release in
17 matches
Mail list logo
