You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by el...@apache.org on 2016/05/04 04:28:55 UTC
svn commit: r1742209 - in /commons/proper/vfs/trunk: RELEASE-NOTES.txt
src/site/xdoc/index.xml
Author: elserj
Date: Wed May 4 02:28:55 2016
New Revision: 1742209
URL: http://svn.apache.org/viewvc?rev=1742209&view=rev
Log:
Documentation changes from 2.1-rc0
Modified:
commons/proper/vfs/trunk/RELEASE-NOTES.txt
commons/proper/vfs/trunk/src/site/xdoc/index.xml
Modified: commons/proper/vfs/trunk/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewvc/commons/proper/vfs/trunk/RELEASE-NOTES.txt?rev=1742209&r1=1742208&r2=1742209&view=diff
==============================================================================
--- commons/proper/vfs/trunk/RELEASE-NOTES.txt (original)
+++ commons/proper/vfs/trunk/RELEASE-NOTES.txt Wed May 4 02:28:55 2016
@@ -190,6 +190,11 @@ o VFS-361: Upgrade commons collections
Removed:
o VFS-469: Remove unused dependency to javax.jcr:jcr.
+Please note that release 2.1 is not completely binary compatible with the previous 2.0 release. This
+is primarily due to the upgrade of Apache Commons Compress to 1.6 and is limited to the TarFileProvider
+and related classes. All other errors reported in the Clirr report should be binary compatible as
+they consist of method additions.
+
Historical list of changes: http://commons.apache.org/proper/commons-vfs/changes-report.html
For complete information on Apache Commons VFS, including instructions on how to submit bug reports,
Modified: commons/proper/vfs/trunk/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/commons/proper/vfs/trunk/src/site/xdoc/index.xml?rev=1742209&r1=1742208&r2=1742209&view=diff
==============================================================================
--- commons/proper/vfs/trunk/src/site/xdoc/index.xml (original)
+++ commons/proper/vfs/trunk/src/site/xdoc/index.xml Wed May 4 02:28:55 2016
@@ -81,8 +81,8 @@
to replace 2.0 with 2.1 without the need for changes to API consumers. VFS 2.1 has introduced some now
methods for provider interfaces (like <code>FileObject</code>). If you implement a VFS provider and use the
corresponding <code>Abstract*</code> or <code>Default*</code> classes, there should be no need to modify
- the code or recompile the provider.
- See the <a href="https://archive.apache.org/dist/commons/vfs/RELEASE_NOTES.txt">Release Notes</a> and the
+ the code or recompile the provider. The TarFileProvider is one known exception to compatibility with 2.0.
+ See the <a href="https://dist.apache.org/repos/dist/dev/commons/vfs/RELEASE-NOTES.txt">Release Notes</a> and the
<a href="commons-vfs2/clirr-report.html">Clirr Report</a> for details. VFS 2.1 adds a new read-only provider
for the Apache Hadoop (HDFS) File system.
</p><p>