[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-1030?page=c...
]
Dmitry Geraskov commented on HBX-1030:
--------------------------------------
Is the problem that exporters do not use the same line separator?
In this case sysEOL patch do not resolve problem. And we need to update all our exporters
to use system line separator. The eol patch can be short-time solution.
Mixed eol chars in generated pojos
----------------------------------
Key: HBX-1030
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-1030
Project: Hibernate Tools
Issue Type: Bug
Components: hbm2java
Affects Versions: 3.2.0.GA
Environment: java
Reporter: Simon Toens
Priority: Minor
Attachments: DocExporterpatch.txt, eol.patch, sysEOL.txt
org.hibernate.tool.hbm2x.pojo.ImportContextImpl hardcodes "\r\n" as eol
characters for import statements. This is kind of lame, and a problem when using svn with
svn:eol-style=native:
$ svn add revengtest/
...
A revengtest/src//test/Actor.hbm.xml
svn: File 'revengtest/src/test/Actor.java' has inconsistent new lines
svn: Inconsistent line ending style
Since the rest of the generated pojo uses "\n", why not just use that?
Attached is the trivial patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira