Author: bayard
Date: Sun Jan 30 09:10:19 2011
New Revision: 1065238
URL: http://svn.apache.org/viewvc?rev=1065238&view=rev
Log:
Minor update
Modified:
commons/proper/lang/trunk/src/site/xdoc/article3_0.xml
Modified: commons/proper/lang/trunk/src/site/xdoc/article3_0.xml
URL:
http://svn.apache.org/viewvc/commons/proper/lang/trunk/src/site/xdoc/article3_0.xml?rev=1065238&r1=1065237&r2=1065238&view=diff
==============================================================================
--- commons/proper/lang/trunk/src/site/xdoc/article3_0.xml (original)
+++ commons/proper/lang/trunk/src/site/xdoc/article3_0.xml Sun Jan 30 09:10:19
2011
@@ -54,10 +54,9 @@ Java 5 we are remove this feature. The d
we are on Java 6, where the last remaining parts of the JDK appear to have
embraced the new cause API. </p>
<p>JVMRandom - This class was introduced in Lang 2.0 to support a Random
object built around the system seed. This
proved to be both an uncommon use case and one with bugs and so was dropped.
</p>
-<p>StringEscapeUtils.escapeSql - This was a misleading method, only handling
the simplest of possible SQL cases. As SQL is not
-Lang's focus, it didn't make sense to improve this method. </p>
+<p>StringEscapeUtils.escapeSql - This was a misleading method, only handling
the simplest of possible SQL cases. As SQL is not Lang's focus, it didn't make
sense to maintain this method. </p>
<p>Various Exception classes were removed - the lesson in defining more
semantically relevant exception classes is that you can keep on coming up with
more and more new classes. Simpler to focus on using the main JDK classes. </p>
-<p>The various Range classes in the <code>math</code> package were removed in
favour of a new Range class. </p>
+<p>The various Range classes in the <code>math</code> package were removed in
favour of a new generic Range class. </p>
<p>All deprecated fields/methods/classes - with a new major version, all of
the previously deprecated parts of the API could finally go away. </p>
<p>If you feel that something was unfairly taken away, please feel free to
contact the list. In many cases the possibility exists to reintroduce code. </p>
</section>
