I just removed some message following your suggestion.
About the 3 MessageWriteToTest test failing I notice that there is an
issue with the QuotedPrintableInputStream(or the output stream, I don't
know). The fact is that at any roundtrip we end with a =0D=0A added to
the end of the quoted printable stream.
Maybe the quoted printable input stream should not the return the last
\r\n, or maybe the outer stream should not give it the last \r\n.
You are more expert than me to understand this.
Robert Burrell Donkin ha scritto:
On Mon, Jul 21, 2008 at 2:37 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Robert Burrell Donkin ha scritto:
i'm dispirited and disappointed. this is a complete mess.
- robert
Can you list them?
Failed tests:
testBinaryAttachmentLenient(org.apache.james.mime4j.message.MessageWriteToTest)
testBinaryAttachmentStrictError(org.apache.james.mime4j.message.MessageWriteToTest)
testBinaryAttachmentStrictIgnore(org.apache.james.mime4j.message.MessageWriteToTest)
mixed-newlines-base64(org.apache.james.mime4j.message.MessageParserTest)
bad-newlines-multiple-parts-base64(org.apache.james.mime4j.message.MessageParserTest)
intermediate-boundaries(org.apache.james.mime4j.message.MessageParserTest)
very-very-long-boundary(org.apache.james.mime4j.message.MessageParserTest)
very-long-boundary(org.apache.james.mime4j.message.MessageParserTest)
mixed-newlines(org.apache.james.mime4j.message.MessageParserTest)
misplaced-boundary(org.apache.james.mime4j.message.MessageParserTest)
weird-boundary(org.apache.james.mime4j.message.MessageParserTest)
ending-boundaries(org.apache.james.mime4j.message.MessageParserTest)
bad-newlines-multiple-parts(org.apache.james.mime4j.message.MessageParserTest)
missing-inner-boundary(org.apache.james.mime4j.message.MessageParserTest)
basic-plain-very-long-lines(org.apache.james.mime4j.message.MessageParserTest)
mixed-newlines-base64(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
bad-newlines-multiple-parts-base64(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
intermediate-boundaries(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
mixed-newlines(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
misplaced-boundary(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
ending-boundaries(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
bad-newlines-multiple-parts(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
missing-inner-boundary(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
basic-plain-very-long-lines(org.apache.james.mime4j.MimeStreamParserExampleMessagesTest)
I have 11 failures.
8 of them are about boundaries and you can see there is an open thread (I
asked you also if you would have preferred me to remove them and attach to
JIRA but you didn't ask that).
i had assumed that they were fixed on the branch
We had a branch for 48 hours. Almost nothing happened there.
is suspect that these tests won't work on linux but i can take a look
into that. it would be much better if the
If they don't work we probably have a different behaviour between
windows and linux, and this would be a bug anyway. It probably was
previously working because the expected resource was committed as text
files so svn was converting the output.
Please provide feedback, or I'll test ASAP as I can get access on my
linux box.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
