Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Thu, 7 Jan 2010 13:21:26 +1100
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
Subject: Re: Java settings
Message-ID: <20100107022126.GD16955@igg.indexgeo.com.au>
References: <20091215082542.6CF3A23888FE@eris.apache.org>
 <20091226223117.GC3093@beaver.dehavilland>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091226223117.GC3093@beaver.dehavilland>
User-Agent: Mutt/1.4.2.3i

Brian M Dube wrote:
> >     forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
> 
> This edit prompted me to browse through this file for the first time
> in a while. I didn't see it noted anywhere to turn off debug symbols
> and to turn on code optimization as part of the test and release
> cycle. Our code base is tiny enough that I don't think this matters
> for us, but does anyone know if our major dependencies (such as
> Cocoon) do this as part of their release? Do we want to for our code?

I don't know the answers to this, not being a real Java person.

In $FORREST_HOME/etc/cocoon_upgrade/local.build.properties
---------
compiler=modern
compiler.debug=on
compiler.optimize=on
compiler.deprecation=off
compiler.nowarn=on
source.vm=1.4
---------

Please do whatever you reckon will assist.

-David