You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Scott Markwell (JIRA)" <ji...@apache.org> on 2018/02/21 21:51:00 UTC

[jira] [Created] (TEXT-119) StringEscapeUtils dropped SQL support but it is not clear if this is intentional or not

Scott Markwell created TEXT-119:
-----------------------------------

             Summary: StringEscapeUtils dropped SQL support but it is not clear if this is intentional or not
                 Key: TEXT-119
                 URL: https://issues.apache.org/jira/browse/TEXT-119
             Project: Commons Text
          Issue Type: Bug
    Affects Versions: 1.2
            Reporter: Scott Markwell


The Commons Text user guide indicates StringEscapeUtils supposed SQL as an escape

[http://commons.apache.org/proper/commons-text/userguide.html]

Commons Lang3 indicates the functionality of org.apache.commons.lang3.StringEscapeUtils was moved to Commons Text (which does include SQL escape) and deprecates it's own implementation.

[http://commons.apache.org/proper/commons-text/changes-report.html] Provides no insight on the lack of SQL support

 

I'm not sure the correct path forward, as project intentions aren't clear.  If the project has no intention of supporting SQL, the user-guide should be updated and notes about migrating from commons-lang3 should note that stance.  Additionally if another Java ASF project is providing that functionality it should be indicated.  If this is an oversight on inclusion in the Commons Text project, then I guess this is a missing feature request.

Thanks for all the great work

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)