War-command fails when the play application is a descendant of a hidden directory
Framework version: 1.2.3
Platform you're using: OSX, Linux
1) mkdir .hidden
2) play new .hidden/my-play-app
3) play war .hidden/my-play-app/ -o my-play-app-deploy
4) ls my-play-app-deploy/WEB-INF/application/
Result: the directory is empty
The war-command fails when the play-application is located in a directory that contains a dot in the path (ie when the play-application is a descendant of a hidden directory).
The specific situation is that you can't use the war-command from a job in Jenkins as the working directory for Jenkins is usually something like /home/jenkins/.hudson/Jobs/my-job/workspace). See also https://groups.google.com/forum/#!searchin/play-framework/jenkins$2...
I've solved this by removing two lines from copy_directory() in Utils.py
if root.find('/.') > -1 or root.find('\\.') > -1: continue
As far as I can see the desired goal to skip hidden directories within the play application itself is accomplished by the regexp in the lines just above.
Comments and changes to this ticket
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.