[
https://issues.apache.org/jira/browse/LUCENE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Parkes updated LUCENE-814:
---------------------------------
Attachment: LUCENE-814.txt
That's cool. Didn't know about the modified task.
Using it does want to create a cache.properties file and it leaves it out
there. This version uses other than the default name (in case that name is used
anywhere else?) and also removes it when it's done. It also deletes it before
it begins. Is that a good thing? Don't know what would happen if it had an old
version ahead of time.
> javacc on Win32 (cygwin) creates wrong line endings - fix them with 'ant
> replace'
> ---------------------------------------------------------------------------------
>
> Key: LUCENE-814
> URL: https://issues.apache.org/jira/browse/LUCENE-814
> Project: Lucene - Java
> Issue Type: Task
> Components: Build
> Environment: Windows, Cygwin
> Reporter: Doron Cohen
> Assigned To: Doron Cohen
> Priority: Minor
> Fix For: 2.2
>
> Attachments: 814.javacc.fixcrlf.common-build.patch,
> 814.javacc.line.ends.patch, LUCENE-814.txt, LUCENE-814.txt
>
>
> "ant javacc" in Windows/Cygwin generates files with wrong line endings (\r
> or \r\n instead of *Nix's \n).
> I managed to get rid of those using perl -p -e 's/(\r\n|\n|\r)/\n/g'
> Some useful info on line ending issues is in
> http://en.wikipedia.org/wiki/Newline
> After wasting some time to get rid of those, I modified javacc-QueryParser
> build.xml task to take care of that.
> So now QueryParser files created with "ant javacc" are fixed (if required) to
> have \n as line ends.
> Should probably do that also for the other javacc targets: javacc-HTMLParser
> and javacc-StandardAnalyzer(?)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
