ok, there are a lot of bugs to add testcases
it was just an example
I know that it is not always possible to create a testcase.
thanks for your help
arnaud
On 2/7/06, Doug Douglass <[EMAIL PROTECTED]> wrote:
> Arnaud,
>
> I'm trying to produce a failing test for MAVEN-1549 using maven 1.0.2.
> Un
Arnaud,
I'm trying to produce a failing test for MAVEN-1549 using maven 1.0.2.
Unfortunately, like Bretts comment to MAVEN-1321 (which 1549
duplicates), I'm unable to reproduce the problem. I'll poke at it some
more, but if I can't reproduce it, I'll have nothing to add to the
touchstone test
No, that's right.
You generate the patch and you attach it to the issue
We'll apply it (after a little review) to the core.
thanks again.
arnaud
On 2/4/06, Doug Douglass <[EMAIL PROTECTED]> wrote:
> Hi Arnaud,
>
> Sure thing, that does seem a much better place to put these things. I
> presume I
Hi Arnaud,
Sure thing, that does seem a much better place to put these things. I
presume I should then do an svn diff and attach the patch to the issue,
or is there another way for the test case to get committed?
Cheers,
Doug
Arnaud HERITIER wrote:
Hi Doug,
Thanks a lot for your help.
Hi Doug,
Thanks a lot for your help.
Your testcases are very useful for us to close the issues.
Can you try (when possible) to create your tests in the touchstone-build :
http://svn.apache.org/viewcvs.cgi/maven/maven-1/core/trunk/src/test/touchstone-build/src/reactor-build/
It will help us
Hey Doug,
We are trying to update all the core plugins for inclusion in m11b3
first, see [1] for a status. But help on the core is certainly
appreciated, feel free to take any open issues that are scheduled for
11b3, if the count there is on zero, we'll cut a release.
Cheers,
Lukas
[1] htt
Hey gang,
What's the status of a 1.1 release?
I thought a release or rc was eminent, but I may have confused that with
all the recent plugin discussions.
I've got some free time and would really like to assist, but in
reviewing JIRA issues for 1.1-beta-3 and 1.1-rc1 I'm finding it hard to
j
