Bug 899246 (JBEWS-217) - EWS - tomcat 6 server.xml with carriage return end-of-lines
Summary: EWS - tomcat 6 server.xml with carriage return end-of-lines
Keywords:
Status: CLOSED DUPLICATE of bug 2040112
Alias: JBEWS-217
Product: JBoss Enterprise Web Server 1
Classification: JBoss
Component: unspecified
Version: EWS 1.0.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EWS 1.0.2
Assignee: Permaine Cheung
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-01 20:16 UTC by Aleksandar Kostadinov
Modified: 2012-11-13 16:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
RHEL and Solaris
Last Closed: 2010-03-02 18:06:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEWS-217 0 None None None Never

Description Aleksandar Kostadinov 2010-03-01 20:16:27 UTC
Date of First Response: 2010-03-02 08:57:37
project_key: JBEWS

Tomcat 6 server.xml has \r end-of-lines. That dos style end-of-lines is inappropriate in UNIX like environment. Tomcat 5 seems fine.

Comment 1 Aleksandar Kostadinov 2010-03-01 21:31:08 UTC
If you are looking at in on solaris, you will not see the issue. I think that on solaris the zip utility translates these to \n only style EOLs but this doesn't happen on RHEL. This is why I haven't noticed it on the solaris platform before. But relying on the zip utility seems like a bad idea to me.
So IMHO better fix it for all platforms rather than RHEL only. Windows is fine with \r\n probably.

Comment 2 Permaine Cheung 2010-03-02 13:57:37 UTC
This is to be fixed for JBPAPP-3653.

Comment 3 Aleksandar Kostadinov 2010-03-02 16:39:50 UTC
Thanks, you can close this one as a duplicate if you wish.

btw I tried to search for such JIRA issue but didn't find anything searching in the EWS component. Should we agree to set EWS (+ anything that also suits) as a component for all EWS related JIRAs so they are findable? Or should I search next time by affected versions?
I would prefer the former as it seems easier and less error prone.

Comment 4 Permaine Cheung 2010-03-02 18:06:00 UTC
Closing as duplicate of JBPAPP-3653.
I've marked the component for 3653 to EWS as well, I usually just bring up all issues for EWS 1.0.2. Anyway, I'll keep that component in mind when filing new EWS jiras. :)


Note You need to log in before you can comment on or make changes to this bug.