This shouldn't be an issue - a number of the dev scripts that are run by core dev's generate warnings if file line endings are incorrect.

However, we don't always immediately fix as whitespace changes tend to do a good job of breaking people's git forks/branches/patches

Reopening since it is about the new Hudson/Phing based build-system.

Setting to resolved / won't fix as there is no plan to migrate to a Phing based build system.
Let's go on using Travis CI and our local builds scripts until someone starts working on another solution.