commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy (*$^¨%`£) (JIRA) <j...@apache.org>
Subject [jira] [Closed] (IO-459) Add WindowsLineEndingInputStream and UnixLineEndingInputStream
Date Mon, 27 Oct 2014 23:41:33 GMT

     [ https://issues.apache.org/jira/browse/IO-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Olivier Lamy (*$^¨%`£) closed IO-459.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.5

applied http://svn.apache.org/r1634738
Thanks!

> Add WindowsLineEndingInputStream and UnixLineEndingInputStream
> --------------------------------------------------------------
>
>                 Key: IO-459
>                 URL: https://issues.apache.org/jira/browse/IO-459
>             Project: Commons IO
>          Issue Type: New Feature
>          Components: Streams/Writers
>            Reporter: Kristian Rosenvold
>            Assignee: Olivier Lamy (*$^¨%`£)
>             Fix For: 2.5
>
>         Attachments: IO-459.patch
>
>
> The enclosed patch adds these files and test cases. 
> There is a use-case for writing these both as InputStream and OutputStream.
> Without any concerns of existing use-cases, the OutputStream is probably the most "correct"
implementation. These two classes originate from apache maven, and existing layering made
it much more practical to do this filtering on the "Input" side of the stream pipeline, which
mandates an inputstream based solution. There should be no technical difference between these,
and it should be trivial to adapt these to output streams. This patch only contains InputStream
versions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message