jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-575) unicode escapes in files generated by JJTree
Date Fri, 17 Oct 2008 08:58:46 GMT

    [ https://issues.apache.org/jira/browse/JCR-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640468#action_12640468
] 

Jukka Zitting commented on JCR-575:
-----------------------------------

This seems to be fixed in JavaCC 4.0, see https://javacc.dev.java.net/issues/show_bug.cgi?id=81

I'll see if we could upgrade our JavaCC dependency.





> unicode escapes in files generated by JJTree
> --------------------------------------------
>
>                 Key: JCR-575
>                 URL: https://issues.apache.org/jira/browse/JCR-575
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, jackrabbit-spi-commons
>         Environment: Windows
>            Reporter: Roberto Fonti
>            Priority: Trivial
>
> Maven build fails on windows machines if sources are located in a directory starting
with a 'u'. This is because files created by JJTree (javacc) put filename and path in a comment
of the generated files, like this:
> /*@bgen(jjtree) Generated By:JJTree: Do not edit this line. D:\usr\projects\workspace\jackrabbit\target\generated-src\main\org\apache\jackrabbit\core\query\sql\JCRSQL.jj
*/
> The \u in interpreted as an escape characted and so you get a 
> "BUILD FAILED ... Invalid escape character"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message