Skip to content
Newer
Older
100644 181 lines (136 sloc) 8.39 KB
7562f0d @ok2c Updated release notes
ok2c authored
1 Release 0.7.2
2 -------------------
3
4 Mime4J is a flexible MIME parsing library written in Java. SAX, DOM and pull parsing styles are
5 supported.
6
7 The 0.7.2 release fixes several non-critical bugs found since release 0.7.1.
8
9
10 Release 0.7.1
11 -------------------
12
13 Mime4J is a flexible MIME parsing library written in Java. SAX, DOM and pull parsing styles are
14 supported.
15
16 The 0.7.1 release fixes several non-critical bugs found since release 0.7.
17
18
bb80382 Updated RELEASE_NOTES.txt to reflect some of the changes currently in…
Stefano Bagnara authored
19 Release 0.7
20 -------------------
21
22 Mime4J is a flexible MIME parsing library written in Java. SAX, DOM and pull parsing styles are
23 supported.
b3d2b07 added notes for next release
Markus Wiederkehr authored
24
bb80382 Updated RELEASE_NOTES.txt to reflect some of the changes currently in…
Stefano Bagnara authored
25 The 0.7 release brings another round of API enhancements, bug fixes and performance optimizations.
26 A major effort has been put in code reorganization, separating parsing code from DOM manipulation
85b04a6 @ok2c Updated release notes for Mime4J 0.7 release
ok2c authored
27 code. Mime4J has been restructured into three separate modules: 'core', 'dom' and 'storage'.
28 The 'core' package provides an event-driven SAX style parser that relies on a callback mechanism
29 to report parsing events such as the start of an entity header the start of a body, etc.
30 The 'dom' package contains base/abstract classes and interfaces for MIME-DOM manipulation aiming
31 to provide the base for a full featured traversable DOM. Per default the Mime4J DOM builder stores
32 content of individual body parts in memory. The 'storage' package provides support for more
33 complex storage backends such on-disk storage systems, overflow on max limit, or encrypted storage
34 through JSSE API.
35
36 Mime4J 0.7 improves support for headless messages, malformed separation between headers and body
37 and adds support for "obsolete" rfc822 syntax (e.g: "Header<somespace>: " style). Parsing
38 performance for quoted printable streams have been considerably improved. A "DecodeMonitor" object
39 has been introduced in most code to define how to deal with malformed input (Lenient vs Strict
40 behaviours). Mime4J 0.7 also provides LenientFieldParser as an alternative to DefaultFieldParser
41 when a higher degree of tolerance to non-severe MIME field format violations is desired.
bb80382 Updated RELEASE_NOTES.txt to reflect some of the changes currently in…
Stefano Bagnara authored
42
43 Upgrade Notes
44 -------------
45
85b04a6 @ok2c Updated release notes for Mime4J 0.7 release
ok2c authored
46 * The default field parsing logic has been moved from AbstractField to DefaultFieldParser.
47 * Low level MIME stream classes have been moved from org.apache.james.mime4j.parser to
48 org.apache.james.mime4j.stream package (Field, RawField, MimeTokenStream, ...)
bb80382 Updated RELEASE_NOTES.txt to reflect some of the changes currently in…
Stefano Bagnara authored
49 * "dom" classes/interfaces have been moved from the .message and .field package to the .dom
50 package tree.
b3d2b07 added notes for next release
Markus Wiederkehr authored
51 * The method decodeBaseQuotedPrintable() of class o.a.j.mime4j.codec.DecoderUtil has been renamed
bb80382 Updated RELEASE_NOTES.txt to reflect some of the changes currently in…
Stefano Bagnara authored
52 in decodeQuotedPrintable().
888f4d0 Added explicit notes about contract change in parser and dom due to f…
Stefano Bagnara authored
53 * Preamble and Epilogue are now correctly handled as optionals and the parser invoke their
54 tokens/events only when they are present in the message. So if your code rely on that events
55 being always called make sure to fix it.
56 * preamble and epilogue Strings in Multipart DOM object are now nullable: an empty preamble is
57 different from no preamble, so we had to update the dom contract to support this difference.
58 Make sure to add null checks if code using multipart.getPreamble and multipart.getEpilogue.
d4ee4c7 Documented headless parsing changes (MIME4J-153 and MIME4J-128)
Stefano Bagnara authored
59 * the first event for headless parsing in MimeTokenStream is not the first BODY event.
60 You should not expect T_START_HEADER/T_END_HEADER any more.
bb80382 Updated RELEASE_NOTES.txt to reflect some of the changes currently in…
Stefano Bagnara authored
61
62 Please also note that as of this release Mime4j requires a Java 1.5 compatible runtime.
39136cc @itstechupnorth Add a note for release notes for next release. MIME4J-134 https://iss…
itstechupnorth authored
63
97219a0 link to release notes
Markus Wiederkehr authored
64 Release 0.6
037460d @itstechupnorth https://issues.apache.org/jira/browse/MIME4J-87 Add a factory for cre…
itstechupnorth authored
65 -------------------
66
c8d8a01 @ok2c Updated 0.6 release notes and added more samples
ok2c authored
67 Mime4J is a flexible MIME parsing library written in Java. SAX, DOM and pull parsing styles are
68 supported.
97219a0 link to release notes
Markus Wiederkehr authored
69
85f44c4 @ok2c Fixed typo
ok2c authored
70 The 0.6 release brings another round of API enhancements and performance optimizations. There has
c8d8a01 @ok2c Updated 0.6 release notes and added more samples
ok2c authored
71 been a number of notable improvements in the DOM support. MIME stream parser is expected to be
4802f06 @ok2c Fixed another typo
ok2c authored
72 50% faster when line counting is disabled. Please also note that as of this release Mime4j
73 requires a Java 1.5 compatible runtime.
97219a0 link to release notes
Markus Wiederkehr authored
74
037460d @itstechupnorth https://issues.apache.org/jira/browse/MIME4J-87 Add a factory for cre…
itstechupnorth authored
75 Notes
76 -----
c95660f @itstechupnorth Added a few more notes based on comments from the list
itstechupnorth authored
77
78 * Mime4j API is still considered unstable and is likely to change in future releases
79 * The DOM API has been now been comprehensively refactored and the known limitations
80 addressed. Please report any remaining issues to
81 https://issues.apache.org/jira/browse/MIME4J.
82 * Some low level functions are available only in the pull parser (recommended for
83 advanced users)
84 * 0.6 contains a mixture of approaches to the parsing of advanced MIME field types.
85 Limitations are known with these approaches with some relatively uncommon use cases.
86 A consistent and comprehensive rewrite is planned for 0.7 which should consolidate
87 and address these.
c500c04 additional release notes for 0.6
Markus Wiederkehr authored
88 * The former interfaces TextBody and BinaryBody have been changed into abstract subclasses
89 of class SingleBody. Code that implements these interfaces has to be changed accordingly.
90 [https://issues.apache.org/jira/browse/MIME4J-111]
91 * A dedicated class for writing a message has been introduced. Class MessageWriter has now
92 to be used instead of Body.writeTo(OutputStream, int). A short-cut method
93 Message.writeTo(OutputStream) without a mode parameter is also available.
94 [https://issues.apache.org/jira/browse/MIME4J-110]
95 * Class NamedMailbox has been removed. Class Mailbox now has an additional name property.
96 [https://issues.apache.org/jira/browse/MIME4J-107]
97 * Class MessageUtils has been removed. The methods and constants can now be found in class
98 CharsetUtil in the same package.
99 [https://issues.apache.org/jira/browse/MIME4J-106]
100 * Package org.apache.james.mime4j.decoder has been renamed in org.apache.james.mime4j.codec.
101 [https://issues.apache.org/jira/browse/MIME4J-105]
102 * Class AbstractBody has been superseded by SingleBody. AbstractBody has been removed.
103 * BodyFactory introduced allowing more flexible storage for Message parts. TempFileTextBody
037460d @itstechupnorth https://issues.apache.org/jira/browse/MIME4J-87 Add a factory for cre…
itstechupnorth authored
104 and TempFileBinaryBody removed.
105 [https://issues.apache.org/jira/browse/MIME4J-87]
c500c04 additional release notes for 0.6
Markus Wiederkehr authored
106 * Mime4j now has a more flexible mechanism for storing message bodies. Class TempStorage
107 has been superseded by StorageProvider in package org.apache.james.mime4j.storage.
108 The classes TempStorage, TempPath, TempFile and SimpleTempStorage have been removed.
109 [https://issues.apache.org/jira/browse/MIME4J-83]
037460d @itstechupnorth https://issues.apache.org/jira/browse/MIME4J-87 Add a factory for cre…
itstechupnorth authored
110 * Temporary text body storage for Message parts now defaults to US-ASCII (was ISO-8859-1)
111
c8d8a01 @ok2c Updated 0.6 release notes and added more samples
ok2c authored
112 Detailed change log can be found here:
113
114 http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310521&styleName=Html&version=12313434
115
116
f206255 @ok2c Updated release notes / status page for the upcoming 0.5 release
ok2c authored
117 Release 0.5
118 -------------------
119
120 Mime4J is a flexible MIME parsing library written in Java. SAX, DOM and pull parsing
121 styles are supported.
122
123
124 The 0.5 release addresses a number of important issues discovered since 0.4. In
125 particular, it improves Mime4j ability to deal with malformed data streams including
126 those intentionally crafted to cause excessive CPU and memory utilization that can
127 lead to DoS conditions.
128
129 This release also fixes a serious bug that can prevent Mime4j from correctly
130 processing binary content.
131
132 Detailed change log can be found here:
133
134 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310521&styleName=Html&version=12313178
135
136 Notes
137 -----
138 * Mime4j API is still considered unstable and is likely to change in future releases
139 * DOM support has known limitations and some roundtrip issues remain to be resolved
140 * Some low level functions are available only in the pull parser (recommended for
141 advanced users)
142
143
144
dee6da7 @ok2c Added release notes; added DOAP descriptor; updated the web site for …
ok2c authored
145 Release 0.4
146 -------------------
147
9906087 @itstechupnorth Added a brief description (users don't always get a library through t…
itstechupnorth authored
148 Mime4J is a flexible MIME parsing library written in Java. SAX, DOM and pull parsing
149 styles are supported.
150
dee6da7 @ok2c Added release notes; added DOAP descriptor; updated the web site for …
ok2c authored
151 The 0.4 release brings a number of significant improvements in terms of
152 supported capabilities, flexibility and performance:
153
154 * Revised and improved public API with support for pull parsing
155
156 * Support for parsing of 'headless' messages transmitted using non SMTP
157 transports such as HTTP
158
159 * Reduced external dependencies. Mime4j is no longer directly dependent on log4j
160 and commons-io
161
162 * Improved parsing performance (up to 10x for large messages)
163
9906087 @itstechupnorth Added a brief description (users don't always get a library through t…
itstechupnorth authored
164 * More comprehensive header parsing including support for RFC1864, RFC2045,
165 RFC2183, RFC2557 and RFC3066
166
167 * Revised packaging and exception hierarchy. MimeException now extends
168 IOException.
169
dee6da7 @ok2c Added release notes; added DOAP descriptor; updated the web site for …
ok2c authored
170 Detailed change log can be found here:
171
172 http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310521&styleName=Html&version=12312483
173
9906087 @itstechupnorth Added a brief description (users don't always get a library through t…
itstechupnorth authored
174 Notes
175 -----
176 * 0.4 contains numerous API improvements and is not binary compatible with 0.3
177 * Mime4j API is still considered unstable and is likely to change in future releases
178 * DOM support has known limitations and some roundtrip issues remain to be resolved
179 * Some low level functions are available only in the pull parser (recommended for
180 advanced users)
Something went wrong with that request. Please try again.