You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/10/17 11:18:44 UTC
[jira] Resolved: (JCR-575) unicode escapes in files generated by
JJTree
[ https://issues.apache.org/jira/browse/JCR-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-575.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Assignee: Jukka Zitting
Fixed in trunk and 1.5 by upgrading to JavaCC 4.0.
> 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
> Assignee: Jukka Zitting
> Priority: Trivial
> Fix For: 1.5.0
>
>
> 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.