The 'problem' is that the \n's that php-shindig produced (and it only adds those when formatting the responses, which it only does when debugging = true ie the default configuration) and the unit tests test against the same.
Another issue with releasing a package with windows line endings is that if someone would ever want to do a patch against a svn checkout, we might risk getting --entire file ++entire file with windows line endings patches Sigh, why is it so hard to do tar c shindig/php | gzip > release.tar.gz in maven, sure makes life more complicated ;/ Please some one find a 'don't touch php files' switch before I regret conceding to using maven for building releases :) On Wed, May 13, 2009 at 4:10 PM, Ian Boston <i...@tfd.co.uk> wrote: > > On 13 May 2009, at 15:01, Chris Chabot wrote: > > is there really no >> exclude_rewrite=*.php flag that can be set somewhere in that mysterious >> maven configuration? >> > > mysterious or magical, hard to tell sometimes :), > we could split the package into text and non text and put the php in the > non text to exclude the php files. > > But that would make the php files in the release depend on the platform the > release was built on. > > What is the eol-style in svn for these files ? > Ian > >
