<commit_before>Upgrading Stripes
http://www.stripesframework.org/

This file documents the steps involved in upgrading an application from Stripes
1.4.x to Stripes 1.5. Since Stripes 1.0-1.4.3 have been backwards compatible it
should be possible to apple these steps to upgrade to Stripes 1.5 from earlier
versions also.

Contents
--------
1. Required Steps
2. Suggested Steps
3. Backwards Incompatibilities

1. Required Steps
   --------------
   -> Replace your existing stripes.jar with the new copy from the lib/ directory
      of the distribution.
   -> Replace your existing commons-logging.jar with the new copy from the lib/
      directory of the distribution
   -> If you are using commons-fileupload download the latest version from the
      apache website http://commons.apache.org/downloads/download_fileupload.cgi

2. Suggested Steps
   --------------
   One significant new feature in Stripes 1.5 that you may wish to leverage at upgrade
   time is the concept of "Extension Packages". Using this feature you can inform Stripes
   of one or more extension packages, e.g.:
       <init-param>
           <param-name>Extension.Packages</param-name>
           <param-value>com.myco.myapp.web.stripesext</param-value>
       <init-param>
       
   If one or more packages are specified Stripes will search these packages for classes
   that implement various interfaces and wire them up without requiring you to configure
   them manually in web.xml. This includes custom:
     -> ActionBeanContext classes
     -> Interceptor classes
     -> ConfigurableComponent classes (e.g. ActionResolvers, LocalePickers)
     
   To reduce your configuration it is recommended that you move any and all such
   custom classes into a single package hierarchy and specify the root package. Once
   done you can remove all web.xml configuration for these custom classes.           

3. Backwards Incompatibilities
   ---------------------------
   Stripes 1.5 is the first major release of Stripes that is not completely
   backwards compatible with earlier versions of Stripes. However most of the
   incompatible change are quite small and require only minor edits to your
   application (often achievable with search & replace functionality). This
   section documents these incompatibilities.
<commit_msg>Added Formatter and TypeConverter classes to the list handled by Extension.Packages<commit_after>Upgrading Stripes
http://www.stripesframework.org/

This file documents the steps involved in upgrading an application from Stripes
1.4.x to Stripes 1.5. Since Stripes 1.0-1.4.3 have been backwards compatible it
should be possible to apple these steps to upgrade to Stripes 1.5 from earlier
versions also.

Contents
--------
1. Required Steps
2. Suggested Steps
3. Backwards Incompatibilities

1. Required Steps
   --------------
   -> Replace your existing stripes.jar with the new copy from the lib/ directory
      of the distribution.
   -> Replace your existing commons-logging.jar with the new copy from the lib/
      directory of the distribution
   -> If you are using commons-fileupload download the latest version from the
      apache website http://commons.apache.org/downloads/download_fileupload.cgi

2. Suggested Steps
   --------------
   One significant new feature in Stripes 1.5 that you may wish to leverage at upgrade
   time is the concept of "Extension Packages". Using this feature you can inform Stripes
   of one or more extension packages, e.g.:
       <init-param>
           <param-name>Extension.Packages</param-name>
           <param-value>com.myco.myapp.web.stripesext</param-value>
       <init-param>
       
   If one or more packages are specified Stripes will search these packages for classes
   that implement various interfaces and wire them up without requiring you to configure
   them manually in web.xml. This includes custom:
     -> ActionBeanContext classes
     -> Interceptor classes
     -> ConfigurableComponent classes (e.g. ActionResolvers, LocalePickers)
     -> Formatter classes
     -> TypeConverter classes
     
   To reduce your configuration it is recommended that you move any and all such
   custom classes into a single package hierarchy and specify the root package. Once
   done you can remove all web.xml configuration for these custom classes.           

3. Backwards Incompatibilities
   ---------------------------
   Stripes 1.5 is the first major release of Stripes that is not completely
   backwards compatible with earlier versions of Stripes. However most of the
   incompatible change are quite small and require only minor edits to your
   application (often achievable with search & replace functionality). This
   section documents these incompatibilities.

{'fraction_non_alphanumeric': 0.07097725358045492, 'fraction_numerical': 0.008845829823083403, 'mean_word_length': 3.01097972972973, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 29, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 4}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 6, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1622380', 'n_tokens_mistral': 1194, 'n_tokens_neox': 1133, 'n_words': 564}