eclipsify: log4j.properties are not recognized in test mode because conf folder is too late on classpath
When running the test launch in eclipse, the log4j.properties file is not recognized because the conf folder is the last classpath entry.
This is the same problem that has already been fixed for the "normal" launch in the commit 129f13.
Will add a pull request soon.
Comments and changes to this ticket
(from [358820adbbf7737103fe6e7527762adb86816b3b]) [#629] Use /conf folder in classpath of test launch before the rest https://github.com/playframework/play/commit/358820adbbf7737103fe6e...
[#629] eclipsify: log4j.properties are not recognized in test mode because conf folder is too late on classpath https://github.com/playframework/play/commit/161bce95c32b14e6dc0cb9...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
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>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>
<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<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.