Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

project asset jar not copied to stage/distribution in a multi-module project #108

Open
gokhanoner opened this issue Jul 17, 2019 · 3 comments

Comments

@gokhanoner
Copy link

gokhanoner commented Jul 17, 2019

Plugin version 0.6

After running gradle stage/dist, I can see that 2 jar files created under build/libs folder, one for jar/scala classes, and one for assets, the public folder. These files are generally web assets, like js/html files. I can see that module jar/asssets files are copied but for main project, only project.jar file present in the build/stage/main/lib, folder, not project-assets.jar. This causes app start but without ant static Web files. When manually copying assets.jar, app works as expected.

@PaulFridrick
Copy link
Contributor

Same problem here, I have all the submodules assets jar in the zip but for the main project the assets jar is missing...

@rt83
Copy link

rt83 commented Oct 15, 2019

I had the same problem. The way I solved it was to set the version before applying the play plugin.

The reason could be as following:

  1. The asset jar to be copied was specified at the moment of the plugin application. The jar name is project-assets.jar
  2. After plugin application is done, a version number is specified, the actual jar created by the task create createPlayAssetsJar then has different name: project-assets-version.jar

This causes the CopySpec to fail because it tried to copy a non-existent file.

@sugarcrm-dmoore
Copy link

id 'org.gradle.playframework' version '0.12' apply false the apply false resolves the issue if anyone is still running into this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants