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

Gary Gregory commented on XALANJ-2573:
--------------------------------------

Depending on compatibility, we should consider using Java's own RE pacakge 
instead. 
                
> update xalan build to include newer version of regexp
> -----------------------------------------------------
>
>                 Key: XALANJ-2573
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2573
>             Project: XalanJ2
>          Issue Type: Wish
>      Security Level: No security risk; visible to anyone(Ordinary problems in 
> Xalan projects.  Anybody can view the issue.) 
>          Components: Xalan
>    Affects Versions: 2.7.1
>            Reporter: Sam Broydo
>            Assignee: Steven J. Hathaway
>
> Current build of xalan-2.7.1.jar includes seemingly jakarta-regexp version 
> 1.2:
> Name: org/apache/regexp/
> Comment: Java Regular Expression package 
> Specification-Title: Java Regular Expression package 
> Specification-Vendor: Apache Software Foundation 
> Specification-Version: 1.2
> Implementation-Title: org.apache.regexp
> This is pretty far from the latest regexp available - 1.5.
> Can you update the build to include latest ?
> The consequences are that some long time fixed regexp bugs are getting 
> exposed though xalan, like :
> Caused By: org.apache.regexp.RESyntaxException: Syntax error: Too many 
> bracketed closures (limit is 10)
>         at org.apache.regexp.RECompiler.syntaxError(RECompiler.java:253)
>         at org.apache.regexp.RECompiler.closure(RECompiler.java:1014)
>         at org.apache.regexp.RECompiler.branch(RECompiler.java:1151)
>         at org.apache.regexp.RECompiler.expr(RECompiler.java:1203)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to