Re: Maven 2.1 Preparation Task List (was: artifact changes)

2007-06-07 Thread Jason van Zyl
On 7 Jun 07, at 4:28 PM 7 Jun 07, John Casey wrote: Sorry, I'm not really following. I understand that this is about integration-testing for Maven itself That's all I was making clear. -john On Jun 7, 2007, at 3:36 PM, Jason van Zyl wrote: On 7 Jun 07, at 3:00 PM 7 Jun 07, John Casey w

Re: Maven 2.1 Preparation Task List (was: artifact changes)

2007-06-07 Thread John Casey
Sorry, I'm not really following. I understand that this is about integration-testing for Maven itself, but IMO the best way to integration-test any Maven system - be it the core or a plugin - is to create a series of builds that use the feature under test. Therefore, core integration-tests

Re: Maven 2.1 Preparation Task List (was: artifact changes)

2007-06-07 Thread Jason van Zyl
On 7 Jun 07, at 3:00 PM 7 Jun 07, John Casey wrote: I'll take the integration-testing tasks. Kenney and I have talked a bit about some of this stuff, so it'd be a natural extension to those discussions. These are specifically out integration tests for Maven itself, not the plugin integ

Re: Maven 2.1 Preparation Task List (was: artifact changes)

2007-06-07 Thread John Casey
I'll take the integration-testing tasks. Kenney and I have talked a bit about some of this stuff, so it'd be a natural extension to those discussions. -john On Jun 6, 2007, at 10:56 PM, Brett Porter wrote: Ok, I pushed all these into the MPA JIRA: http://jira.codehaus.org/secure/IssueNavi

Re: Maven 2.1 Preparation Task List (was: artifact changes)

2007-06-06 Thread Brett Porter
Ok, I pushed all these into the MPA JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=true&mode=hide&sorter/order=DESC&sorter/ field=priority&resolution=-1&pid=10332&fixfor=13535 I've taken for myself: - Come up with a minimal workflow for JIRA - Clean up JIRA (not going to do i

Re: artifact changes

2007-06-06 Thread Brett Porter
On 07/06/2007, at 12:55 AM, Jason van Zyl wrote: I stand by my case that all of us should be working on this list to put us in a position to talk in a meaningful way about any implementation of anything being replace. In that case... I would like to champion the re-initiation of the devel

Re: artifact changes

2007-06-06 Thread Jason van Zyl
On 6 Jun 07, at 12:55 AM 6 Jun 07, Brett Porter wrote: On 06/06/2007, at 2:06 PM, Jason van Zyl wrote: Is this different/related to the design paper you were working on? As I've said before, I'm interested in collaborating on this, and would like to see it posted somewhere. No, he sta

Re: artifact changes

2007-06-05 Thread Brett Porter
On 06/06/2007, at 2:06 PM, Jason van Zyl wrote: Is this different/related to the design paper you were working on? As I've said before, I'm interested in collaborating on this, and would like to see it posted somewhere. No, he started on this prior to what I started. I have the underly

Re: artifact changes

2007-06-05 Thread Jason van Zyl
On 5 Jun 07, at 11:33 PM 5 Jun 07, Brett Porter wrote: On 06/06/2007, at 5:48 AM, Jason van Zyl wrote: John has started an API cleanup for artifact resolution and one is slated for maven-project but the second we promote these we are really bound to support them and the one that are there

Re: artifact changes

2007-06-05 Thread Brett Porter
On 06/06/2007, at 5:48 AM, Jason van Zyl wrote: John has started an API cleanup for artifact resolution and one is slated for maven-project but the second we promote these we are really bound to support them and the one that are there now are unsupportable. Is this different/related to t