#324 confirmed

precompile folder missed in war generation

Reported by Otann | October 23rd, 2010 @ 09:09 PM

Precompile classes are missing in war output folder.
I've discovered that when I was trying to deploy test app to Google App Engine.
Both ways (via gae plugin and via App Engine SDK) uploaded application, but is returned Error 500 anyway.

Framework version: 1.1RC3

Platform you're using: Mac OS X 10.6.4

Reproduction steps:

play new test
play war test test.war
cd test
play gae:deploy


In App Engine logs i've discovered that precompiled classes are missing.
So I manually added precompile classes to war folder (they are generated but not copied) and manually deployed with App Engine SDK.
Application loaded and showed "Your application is ready !" page.

It looks like in utils.py, in line 73:

def package_as_war(app, env, war_path, war_zip_path):
you guys are just missing whole precompiled folder

Maybe I am doing something wrong, but I have no idea, how other people deal with that via gae plugin.

Comments and changes to this ticket

  • setter

    setter October 28th, 2010 @ 11:20 AM

    Same problem for me (Mac OSX 10.6.4)

    play 1.1RC3

    0-28 04:14AM 52.373
    play.Logger info: Play! is running in Google App Engine
    I 10-28 04:14AM 52.696
    play.Logger info: Starting /base/data/home/apps/*****/2.345815824515018136/WEB-INF/application
    W 10-28 04:14AM 52.697
    play.Logger warn: No tmp folder will be used (cannot create the tmp dir)
    I 10-28 04:14AM 52.700
    play.Logger info: Module gae is available (/base/data/home/apps/******/2.345815824515018136/WEB-INF/application/../modules/gae-head)
    E 10-28 04:14AM 52.964
    play.Logger error: Precompiled classes are missing!!
    E 10-28 04:14AM 53.739
    play.Logger niceThrowable: 
    Internal Server Error (500)
    Unexpected error
    Unexpected error : Application is not started
  • Otann

    Otann October 28th, 2010 @ 01:28 PM

    There is "workaround" for that.
    Just edit file ${play.home}/modules/gae-head/commands.py near line 83 from

    war_path = os.path.join(tempfile.gettempdir(), '%s.war' % os.path.basename(app.path))
    package_as_war(app, env, war_path, None)


    war_path = os.path.join(tempfile.gettempdir(), '%s.war' % os.path.basename(app.path))
    # precompiled dir fix
    if os.path.isdir(war_path):
    shutil.copytree(os.path.join(app.path, 'precompiled'), os.path.join(war_path, 'WEB-INF/precompiled'))
    # end of fix
    package_as_war(app, env, war_path, None)
  • Nicolas Leroux

    Nicolas Leroux July 26th, 2011 @ 08:51 PM

    • Assigned user set to “Nicolas Leroux”
    • State changed from “new” to “confirmed”

    I think this is fixed but it needs to be checked.

  • Danni Justice

    Danni Justice February 12th, 2018 @ 01:30 PM

    Informative reading about precompile folder missed in war generation for custom assignment writing. I hope to read a lot more on this folder share, looking forward to more on it.

  • sdasfdf

    sdasfdf June 6th, 2018 @ 04:34 PM

    UC Browser
    MX Player Thanks for sharing.I found a lot of interesting information here. A really good post, very thankful and hopeful that you will write many more posts like this one.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.