We added the following test (which fails) to demonstrate the
bug. It is not included in the patch because the test creates a
file and we assumed it might need to be modified if it were to be
used in the project test suite:

Details:
We initially ran into an issue when trying to use an antify
generated build.xml to run play ant targets.

play.libs.IO.readContentAsString(File file, String
encoding) uses PrintWriter println() instead of
PrintWriter write() to add file content to the result.
This results in a newline character at the end of the returned
String. We came to this conclusion while trying to debug why
play.ant.PlayConfigurationLoadTask.execute() was not
loading our modules. It turned out a newline was being added to the
filepath play.ant.PlayConfigurationLoadTask.modules()
was reading out of the modules/ file. This lead us to
IO.readContentAsString and the fix.

Comments and changes to this ticket

A playground is opted for the flow of the characteristics for
the people. The utility and https://www.essay-to-go.net is
visited for the reflections for the humans. Citizenship is opted
for the future times.

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.