That would probably be helpful thanks, that will certainly get it
recorded.
Andy
On 16 Mar 2007, at 18:14, Brian E. Fox wrote:
Should we file a 2.0.6 defect for this and link it to PLX-287?
Technically something needs to happen in Maven for this to get
fixed (ie
update the pom)
-----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 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 be grasping, but we are still
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 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 then work the next three weeks to resolve them and do another
release in 4 weeks.
We can try the voting thing like we do with the plugins, or people
can
bring up issues and it's first come first serve. You can pick from
here:
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&resolution=-1&fixfor=13141&sorter/
field=priority&sorter/order=DESC
Or if you know that an issue has been the wrong fix version tell us.
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 make this easier I have created a self-
contained, fully working of example of our integration tests:
http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/
core-integration-test-sample
or
http://idisk.maven.org/jvanzyl/Public/maven-integration-tests/core-
integration-test-sample.zip
Anyone who produces an integration using this form I guarantee your
patches will go to the front of the line. I know that many people
contribute time to fix things and are frustrated when we don't apply
patches, but it also very frustrating for us to try and piece
together
comments and bits of code cobbled together in JIRA. I'm hoping that
this will help. Our integration testing strategy is not fully fleshed
out but what's in that example is what we are using today and them
being all the same as we can move them all forward together when we
improve it.
Even for issue where you don't have a solution providing a test where
we can at least accurately reproduce the problem is immensely
helpful.
I will make an archetype of this example but I wanted to get this
mail
out to get the ball rolling for 2.0.6 so you can take the svn
checkout
or the zip.
I have not forgotten about poor MNG-1577 :-)
Jason.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
