-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
sbt-native-packager doesn't copy configuration when play plugin is enabled #4242
Comments
I suspect that this is |
Yes, this is in 1.0.0 and play 2.4-M3. Should have mentioned that, sorry. @huntc I'm not sure what you mean, which mappings? |
The native packager source directory in Play is the |
@jroper Thanks! That worked. Also I noticed in the latest play docs (master) it says to put it in |
Fixes playframework#4242 Also moved configuration of the dist folder to the PlayLayoutPlugin, so that if disabled, it will revert to the standard `src/universal`.
Pull request here: #4251 |
Fixes playframework#4242 Also moved configuration of the dist folder to the PlayLayoutPlugin, so that if disabled, it will revert to the standard `src/universal`.
Fixes playframework#4242 Also moved configuration of the dist folder to the PlayLayoutPlugin, so that if disabled, it will revert to the standard `src/universal`.
Fixes playframework#4242 Also moved configuration of the dist folder to the PlayLayoutPlugin, so that if disabled, it will revert to the standard `src/universal`.
Fixes playframework#4242 Also moved configuration of the dist folder to the PlayLayoutPlugin, so that if disabled, it will revert to the standard `src/universal`.
The sbt-native-packager docs say here that you can create an
application.ini
insrc/universal/conf
and it will process it and put it in the app'sconf
directory. When the play plugin is enabled this file does not end up in the conf directory. The sbt guys said this seems to be a problem with play.https://github.com/Kyprus/sbt-native-packager-test demonstrates the issue
The text was updated successfully, but these errors were encountered: