[GRADLE-3365] Play resources do not honor nested directories Created: 18/Nov/15  Updated: 18/Nov/15  Resolved: 18/Nov/15

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 2.10-rc-1

Type: Bug
Reporter: Gary Hale Assignee: Gary Hale
Resolution: Fixed Votes: 0


 Description   

Reported on forums at https://discuss.gradle.org/t/play-plugin-does-not-keep-directory-structure-of-resource-files/11933:

When packaging a Play application, if the resource directory conf/ has the following structure:

conf/
routes
evolutions/
default/
1.sql
2.sql
3.sql
I expect the createPlayBinaryJar task to create a jar that maintains the directory structure.

However, currently, the generated jar contains all resource files at the root, i.e.,

% jar -tf build/playBinary/lib/application.jar
META-INF/
META-INF/MANIFEST.MF
[...]
routes
1.sql
2.sql
3.sql
This causes Play database evolutions to silently fail because the evolution scripts cannot be found in evolutions/

{database name}

/.



 Comments   
Comment by Gary Hale [ 18/Nov/15 ]

Resolved with https://github.com/gradle/gradle/pull/528

Generated at Wed Jun 30 12:46:53 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.