svn commit: r1555071 - /myfaces/tobago/trunk/src/site/apt/migration-2.0.apt

[lo...@apache.org]

Author: lofwyr
Date: Fri Jan  3 12:23:12 2014
New Revision: 1555071

URL: http://svn.apache.org/r1555071
Log:
deprecation jar

Modified:
    myfaces/tobago/trunk/src/site/apt/migration-2.0.apt

Modified: myfaces/tobago/trunk/src/site/apt/migration-2.0.apt
URL: http://svn.apache.org/viewvc/myfaces/tobago/trunk/src/site/apt/migration-2.0.apt?rev=1555071&r1=1555070&r2=1555071&view=diff
==============================================================================
--- myfaces/tobago/trunk/src/site/apt/migration-2.0.apt (original)
+++ myfaces/tobago/trunk/src/site/apt/migration-2.0.apt Fri Jan  3 12:23:12 2014
@@ -76,7 +76,7 @@ Facelets
 
    * Remove or replace the <<<facelets.*>>> entries from the <<<web.xml>>> file.
 
-   * Rename all JSTL deklarations from <<<xmlns:c="http://java.sun.com/jstl/core">>> to <<<xmlns:c="http://java.sun.com/jsp/jstl/core">>> in the Facelets.
+   * Rename all JSTL declarations from <<<xmlns:c="http://java.sun.com/jstl/core">>> to <<<xmlns:c="http://java.sun.com/jsp/jstl/core">>> in the Facelets.
 
    * Ensure the version of the faces-config tag in the faces-config.xml is at least 2.0.
 
@@ -88,6 +88,10 @@ Deprecated
    logging warning when using deprecated code via the <<<Deprecation>>> logging category.
    Before and after migrating you should check your application about that.
 
+   For the migration phase you may add the tobago-deprecation.jar as dependency to your project. It contains classes
+   that has been moved (e. g. to the new internal package) or removed. So you can resolve any migration steps step by
+   step. It is not recommended to use the tobago-deprecation.jar for production.
+
 Internal
 
    The package <<<org.apache.myfaces.tobago.internal>>> contains classes that should not be used directly in an application.