Bytecode cache not being created on start about play1 HOT 4 CLOSED

@asolntsev ok thanks, I guess that makes sense. But i don’t think it’s obvious that precompile is the recommended way to deploy. Maybe it would be worth reviewing the deployment documentation to be a bit more explicit with that.

I’ve managed to get my app to precompile and run on the server. I still need to tidy things up, and have a few performance issues, but it looks like I’m nearly there.

Thanks for your help!

from play1.

@bigclumsyoaf When you start Play application in production mode, it's assumed the application should be precompiled by this moment. Did you run play precompile before play start?

from play1.

@asolntsev No, is that mandatory now? It’s not something we ever did on play1.0, 1.2 or 1.3 apps we have in production.

The code seems to handle precompile and compile under start differently, so assumed that both were acceptable.

I did try running precompile while trying to get it to work, but received a different problem. I will need to check the specific error, but from memory it was a problem with commons io FileUtils, but that might have been a conflict with something under the app.

from play1.

@bigclumsyoaf I don't remember if it's officially mandatory, but at least it seems reasonable to me.

Starting in "Production mode" means that everything should be ready for start: the code is compiled etc.

We even did a special move to eliminate from production build eclipse compiler and other dependencies needed only for compilation. It eliminates the risk that hacker manages to generate HTML file with a hacky groovy code in temporary folder and forces Play to compile it (in fact, we had such a vulnerability in production).

from play1.