Yeah, it'd be great to document that. Perhaps I can get the PR in first and then we can created another? I feel that they'll be a few other things along the way to Activator 1.0, Play 2.2 anyhow.

On 17/07/2013, at 9:46 PM, Josh Suereth <notifications@github.com> wrote:

> In documentation/manual/detailledTopics/production/ProductionDist.md:
> 
> > @@ -14,27 +14,42 @@ In the Play console, simply type `dist`:
> >  
> >  [[images/dist.png]]
> >  
> > -> one can easily use an external application.conf by using a special system property called ```conf.file```, so assuming your production ```application.conf``` is stored under your home directory, the following command should create a play distribution using the custom ```application.conf```:_ 
> > +This produces a ZIP file containing all JAR files needed to run your application in the `target/universal` folder of your application. Alternatively you can run `play dist` directly from your OS shell prompt, which does the same thing:
> > +
> > +```bash
> > +$ play dist
> > +```
> > +
> > +> For Windows users a start script will be produced with a .bat file extension. Use this file when running a Play application on Windows.
> > +>
> > +> For Unix users, zip files do not retain Unix file permissions so when the file is expanded the start script will be required to be set as an executable:
> Actually, I think I was using commons-compress at some point, so for linux users, the Info-Zip headers are in place. It's just mac where they don't show up :)
> 
> That said, do you want me to document the "useNativeZip" settings? It will shell out to the linux "zip" command instead of using Java's, which places the magic bits in place to preserve permissions (we use this on activator + typesafe console).
> 
> —
> Reply to this email directly or view it on GitHub.
>