Iacopo
Iacopo
This becomes even more painful when using gradle - no workaround to be found there :(
I'm having the same problem while upgrading to play 2.6 and scala 2.12 - also the project is gradle-based so I was wondering if there's any workaround for gradle. I...
`defaultImports` seems to be using only the enum public enum TwirlImports { SCALA, JAVA }
I was following your PR, thanks a lot @mihaisoloi !
Hey @JLLeitschuh, I was able to pinpoint the issue to an incompatibility with the [ospackage-application plugin](https://github.com/nebula-plugins/gradle-ospackage-plugin/wiki/Provided-Plugins#ospackage-application-plugin): as soon as the plugin is added, the `core.jar` and `core-assets.jar` files are staged....
After some investigation, I'm going to answer my own question: 1. the problem is with the fact that both plugins add to the default `main` distribution of the project 2....
It's not a bug of the `playframework` plugin per se, but one that pops up if it is used with another plugin that modifies the project's standard `distribution` configuration. I...
Hey @big-guy thanks for explaining this - I'll see if I have more time to dig into this, but as of now we're working around the mis-configured distribution to remove...