You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2007/06/07 04:56:42 UTC
Re: Maven 2.1 Preparation Task List (was: artifact changes)
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 it all, but propose the best way to
move forward)
I assigned these to Jason since they are in progress already:
- Apply remaining patches in MNG JIRA
- release Maven 2.0.7
- Finalise and document taxonomy
Any other volunteers?
Cheers,
Brett
On 07/06/2007, at 1:27 AM, Brett Porter wrote:
>
> 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 development
>>> process we started some time back. I think we need to have a
>>> point where we say "from this time on, only a certain level of
>>> quality is acceptable" - and be prepared to reject changes that
>>> don't come with tests, etc. I think it ties in to what you're
>>> doing, so I'll get stuck into that document again.
>>>
>
> and ...
>>>
>>> Should we have these listed as tasks that can be assigned to people?
>>>
>
> WDYT?
>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.1 Preparation Task List (was: artifact changes)
Posted by Jason van Zyl <ja...@maven.org>.
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 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 integration testing just so that's clear.
>>
>> I would like a hybrid of what we had where a good chunk of it was
>> declarative and I would also like to put the individual test with
>> the test. In order the match an archetype for an IT. We would have
>> to do a bit of work to make them all run together but that would
>> take 5 minutes to code up. I find the current structure a little
>> cumbersome.
>>
>>> -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/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 it all, but propose the best
>>>> way to move forward)
>>>>
>>>> I assigned these to Jason since they are in progress already:
>>>> - Apply remaining patches in MNG JIRA
>>>> - release Maven 2.0.7
>>>> - Finalise and document taxonomy
>>>>
>>>> Any other volunteers?
>>>>
>>>> Cheers,
>>>> Brett
>>>>
>>>> On 07/06/2007, at 1:27 AM, Brett Porter wrote:
>>>>
>>>>>
>>>>> 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 development
>>>>>>> process we started some time back. I think we need to have a
>>>>>>> point where we say "from this time on, only a certain level
>>>>>>> of quality is acceptable" - and be prepared to reject changes
>>>>>>> that don't come with tests, etc. I think it ties in to what
>>>>>>> you're doing, so I'll get stuck into that document again.
>>>>>>>
>>>>>
>>>>> and ...
>>>>>>>
>>>>>>> Should we have these listed as tasks that can be assigned to
>>>>>>> people?
>>>>>>>
>>>>>
>>>>> WDYT?
>>>>>
>>>>> - Brett
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> ---
>>> John Casey
>>> Committer and PMC Member, Apache Maven
>>> mail: jdcasey at commonjava dot org
>>> blog: http://www.ejlife.net/blogs/john
>>>
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.1 Preparation Task List (was: artifact changes)
Posted by John Casey <jd...@commonjava.org>.
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 should look a
lot like plugin integration-tests, and all of them should probably
use a common infrastructure (at least to a certain extent).
I'm not sure what you're saying about test locations or whether
they're declarative. Can you elaborate a little bit more? IMO, the
integration tests should be self-contained so they can be generated
using a simple archetype. Then, it would probably require a little
bit of extra code in the test harness to traverse all IT projects and
execute the test.
-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 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 integration testing just so that's clear.
>
> I would like a hybrid of what we had where a good chunk of it was
> declarative and I would also like to put the individual test with
> the test. In order the match an archetype for an IT. We would have
> to do a bit of work to make them all run together but that would
> take 5 minutes to code up. I find the current structure a little
> cumbersome.
>
>> -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/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 it all, but propose the best way
>>> to move forward)
>>>
>>> I assigned these to Jason since they are in progress already:
>>> - Apply remaining patches in MNG JIRA
>>> - release Maven 2.0.7
>>> - Finalise and document taxonomy
>>>
>>> Any other volunteers?
>>>
>>> Cheers,
>>> Brett
>>>
>>> On 07/06/2007, at 1:27 AM, Brett Porter wrote:
>>>
>>>>
>>>> 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 development
>>>>>> process we started some time back. I think we need to have a
>>>>>> point where we say "from this time on, only a certain level of
>>>>>> quality is acceptable" - and be prepared to reject changes
>>>>>> that don't come with tests, etc. I think it ties in to what
>>>>>> you're doing, so I'll get stuck into that document again.
>>>>>>
>>>>
>>>> and ...
>>>>>>
>>>>>> Should we have these listed as tasks that can be assigned to
>>>>>> people?
>>>>>>
>>>>
>>>> WDYT?
>>>>
>>>> - Brett
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> ---
>> John Casey
>> Committer and PMC Member, Apache Maven
>> mail: jdcasey at commonjava dot org
>> blog: http://www.ejlife.net/blogs/john
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Re: Maven 2.1 Preparation Task List (was: artifact changes)
Posted by Jason van Zyl <ja...@maven.org>.
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 integration testing just so that's clear.
I would like a hybrid of what we had where a good chunk of it was
declarative and I would also like to put the individual test with the
test. In order the match an archetype for an IT. We would have to do
a bit of work to make them all run together but that would take 5
minutes to code up. I find the current structure a little cumbersome.
> -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/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 it all, but propose the best way
>> to move forward)
>>
>> I assigned these to Jason since they are in progress already:
>> - Apply remaining patches in MNG JIRA
>> - release Maven 2.0.7
>> - Finalise and document taxonomy
>>
>> Any other volunteers?
>>
>> Cheers,
>> Brett
>>
>> On 07/06/2007, at 1:27 AM, Brett Porter wrote:
>>
>>>
>>> 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 development
>>>>> process we started some time back. I think we need to have a
>>>>> point where we say "from this time on, only a certain level of
>>>>> quality is acceptable" - and be prepared to reject changes that
>>>>> don't come with tests, etc. I think it ties in to what you're
>>>>> doing, so I'll get stuck into that document again.
>>>>>
>>>
>>> and ...
>>>>>
>>>>> Should we have these listed as tasks that can be assigned to
>>>>> people?
>>>>>
>>>
>>> WDYT?
>>>
>>> - Brett
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.1 Preparation Task List (was: artifact changes)
Posted by John Casey <jd...@commonjava.org>.
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/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 it all, but propose the best way
> to move forward)
>
> I assigned these to Jason since they are in progress already:
> - Apply remaining patches in MNG JIRA
> - release Maven 2.0.7
> - Finalise and document taxonomy
>
> Any other volunteers?
>
> Cheers,
> Brett
>
> On 07/06/2007, at 1:27 AM, Brett Porter wrote:
>
>>
>> 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 development
>>>> process we started some time back. I think we need to have a
>>>> point where we say "from this time on, only a certain level of
>>>> quality is acceptable" - and be prepared to reject changes that
>>>> don't come with tests, etc. I think it ties in to what you're
>>>> doing, so I'll get stuck into that document again.
>>>>
>>
>> and ...
>>>>
>>>> Should we have these listed as tasks that can be assigned to
>>>> people?
>>>>
>>
>> WDYT?
>>
>> - Brett
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john