Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-12 Thread Brett Porter
I don't see the need for either, since the trunk set is a superset of what is on the branch. Kenney Westerhof wrote: On Mon, 12 Jun 2006, Carlos Sanchez wrote: Just tossing in an idea: Perhaps a more sophisticated system where you specify which version of maven is needed for the it test - esp

Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-12 Thread Kenney Westerhof
On Mon, 12 Jun 2006, Carlos Sanchez wrote: Just tossing in an idea: Perhaps a more sophisticated system where you specify which version of maven is needed for the it test - especially useful for new feature testing that's not available in some versions of m2. So instead of #commenting out you hav

Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-12 Thread Carlos Sanchez
I think the question here is, should we merge the itxxx folders and then just have the test deactivated in the branch? that would make the differencies between trunk and branch minimal which I see as a good thing (TM) On 6/12/06, Brett Porter <[EMAIL PROTECTED]> wrote: jerome lacoste wrote: > So

Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-11 Thread Brett Porter
jerome lacoste wrote: Someone might want to create a test case for a branch issue without looking at the trunk. And it's better to keep itest ids synchronized. That would be against our development practices we agreed on a while back (everything goes through trunk). The only scenario would b

Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-11 Thread jerome lacoste
On 6/9/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote: On Fri, 9 Jun 2006, Carlos Sanchez wrote: Carlos, > Kenney, could you check it0105 and it0107 and merge its revisions them > to the 2.0.x branch, or does it not apply? it0107 is related to MNG-2293 which is only applied to trunk, so that o

Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-09 Thread Kenney Westerhof
On Fri, 9 Jun 2006, Carlos Sanchez wrote: [snip] > > it0105.. that's a long time ago. Looking at the issue (MRESOURCES-18), > > it's intended for 2.2 (although it's fixed in trunk so it'll be in 2.1 > > too). > > > > I haven't found the cause for this bug yet, but the problem does not > > occur i

Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-09 Thread Carlos Sanchez
On 6/9/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote: On Fri, 9 Jun 2006, Carlos Sanchez wrote: Carlos, > Kenney, could you check it0105 and it0107 and merge its revisions them > to the 2.0.x branch, or does it not apply? it0107 is related to MNG-2293 which is only applied to trunk, so that o

Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-09 Thread Kenney Westerhof
On Fri, 9 Jun 2006, Carlos Sanchez wrote: Carlos, > Kenney, could you check it0105 and it0107 and merge its revisions them > to the 2.0.x branch, or does it not apply? it0107 is related to MNG-2293 which is only applied to trunk, so that one doesn't make any sense to commit to the 2.0.x branch.

Merge it0105 and it0107 to 2.0.x branch

2006-06-09 Thread Carlos Sanchez
Kenney, could you check it0105 and it0107 and merge its revisions them to the 2.0.x branch, or does it not apply? Thanks -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride -