Yes, it could be a good idea to have a property to define the filter for files to change EOL. Is there someone who can open an issue ? I'll do it in the next days.
Arnaud > -----Message d'origine----- > De : Phil Steitz [mailto:[EMAIL PROTECTED] > Envoyé : mardi 15 novembre 2005 06:32 > À : Jakarta Commons Developers List > Objet : Re: [maven] dist plugin for zip-crlf conversation > (was: [vfs][VOTE] release version 1.0) > > On 11/14/05, Stephen Colebourne <[EMAIL PROTECTED]> wrote: > > Phil Steitz wrote: > > > That will screw up diffs, won't it? Probably best to leave the > > > sources along and just apply to .txt files, as the > current version > > > does. > > Not sure about that. When I use subversion to get files they end up > > with Windows EOL. I think thats what we are trying to replicate. > > We should be consistent in any case. Right now the Ant build > for [collections] does this: > > <fixcrlf srcdir="${build.dist.src.work}" eol="crlf" > includes="*.txt,*.properties" /> > and [io] does this > <fixcrlf srcdir="${dist.src}" eol="crlf" > includes="*.txt,*.xml,*.css,*.properties" /> > > Neither appear to mess with the java sources. Do many people > open the java files in windows editors not capable of > handling lf line endings? > > Could be the right solution for the maven dist plugin is to > expose a property that holds the filter. > > Phil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
