Not sure how you compare things in your assertions, but it may be
someone in your team who has different svn client settings (EOL style)
or not the correct encoding for the files. This is a certain way to
get strange test results. Write the comparison strings to a file and
open it with a hex editor
I'll wait and see if someone out there happens to see my email and knows an
answer.
Thanks for taking the time to answer me anyway. :)
Chris
On 10/07/09 1:47 PM, "Wayne Fay" wrote:
> So does that mean M1 is no longer supported?
There are just a lot fewer people on this list using M1 than in
> So does that mean M1 is no longer supported?
There are just a lot fewer people on this list using M1 than in the
past. So don't be surprised when it takes longer than 24 hrs to get a
response to an M1 question. And, you may never get a response, but
that's true for M2 also.
Wayne
-
So does that mean M1 is no longer supported?
C
On 10/07/09 10:06 AM, "Wayne Fay" wrote:
> No one has seen this at all?
Very few people are running M1 at this point, IME.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@mav
> No one has seen this at all?
Very few people are running M1 at this point, IME.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
No one has seen this at all?
Chris
On 9/07/09 2:53 PM, "Dunstall, Christopher" wrote:
Hi,
Lately, I've been getting some really bizarre behaviour from running junit
tests in Maven 1.0.2.
The tests were written in Eclipse, where they run fine. However, when I run a
maven target, it runs th
Hi,
Lately, I've been getting some really bizarre behaviour from running junit
tests in Maven 1.0.2.
The tests were written in Eclipse, where they run fine. However, when I run a
maven target, it runs the junit test but shows an error. As a result, it
finishes up as the build has failed.
