commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pascal Schumacher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEXT-119) StringEscapeUtils dropped SQL support but it is not clear if this is intentional or not
Date Wed, 04 Apr 2018 11:24:00 GMT

    [ https://issues.apache.org/jira/browse/TEXT-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425354#comment-16425354
] 

Pascal Schumacher commented on TEXT-119:
----------------------------------------

Thanks for reporting!

As far as I know neither commons-lang3 nor commons-text never supported SQL escaping. Commons-lang
2.x supported SQL escaping, but this was dropped in 3.0, see https://commons.apache.org/proper/commons-lang/article3_0.html
for details.

I'm not aware of any other Java ASF project is providing this functionally, but there are
a lot of projects so I may miss something.

I have removed the mention of SQL escaping from the commons-text userguide.

> 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
>            Priority: Major
>              Labels: docuentation, roadmap
>             Fix For: 1.4
>
>
> 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)

Mime
View raw message