You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by rd...@apache.org on 2009/02/10 00:09:46 UTC
svn commit: r742784 - /james/mime4j/trunk/RELEASE_NOTES.txt
Author: rdonkin
Date: Mon Feb 9 23:09:46 2009
New Revision: 742784
URL: http://svn.apache.org/viewvc?rev=742784&view=rev
Log:
Added a few more notes based on comments from the list
Modified:
james/mime4j/trunk/RELEASE_NOTES.txt
Modified: james/mime4j/trunk/RELEASE_NOTES.txt
URL: http://svn.apache.org/viewvc/james/mime4j/trunk/RELEASE_NOTES.txt?rev=742784&r1=742783&r2=742784&view=diff
==============================================================================
--- james/mime4j/trunk/RELEASE_NOTES.txt (original)
+++ james/mime4j/trunk/RELEASE_NOTES.txt Mon Feb 9 23:09:46 2009
@@ -11,6 +11,17 @@
Notes
-----
+
+ * Mime4j API is still considered unstable and is likely to change in future releases
+ * The DOM API has been now been comprehensively refactored and the known limitations
+ addressed. Please report any remaining issues to
+ https://issues.apache.org/jira/browse/MIME4J.
+ * Some low level functions are available only in the pull parser (recommended for
+ advanced users)
+ * 0.6 contains a mixture of approaches to the parsing of advanced MIME field types.
+ Limitations are known with these approaches with some relatively uncommon use cases.
+ A consistent and comprehensive rewrite is planned for 0.7 which should consolidate
+ and address these.
* The former interfaces TextBody and BinaryBody have been changed into abstract subclasses
of class SingleBody. Code that implements these interfaces has to be changed accordingly.
[https://issues.apache.org/jira/browse/MIME4J-111]