Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <434BE5DE.2010005@wiu.edu>
Date: Tue, 11 Oct 2005 11:18:38 -0500
From: scott hutinger <S-Hutinger@wiu.edu>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: Beginner question about building Derby myself
References: <434AF04D.2030409@amberpoint.com>
In-Reply-To: <434AF04D.2030409@amberpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

This should have a jira issue to track it, and let people know about 
it.  It may have been missed by people that need to see it.

scott

Bryan Pendleton wrote:

> > For the  2904165 build - did you compile the classes with both
> > debug=false, and sane=false in your  ant.properties ?
> > I suspect the 2904165 size is probably because the classes were 
> built with debug=true
> >
> > Sunitha.
>
> Yes, you are exactly right. Re-building with debug=false in
> my ant.properties causes me to get jar files that are basically
> identical in size to the ones from the binary distribution.
>
> May I suggest that a paragraph about "debug=true/false" be added
> to section 3.2 of
> http://svn.apache.org/repos/asf/db/derby/code/trunk/BUILDING.txt,
> as I completely was unaware that I could set a debug property in
> my ant.properties file.
>
> Something like:
>
>   - debug
>
>     This variable defines whether the java compiler should be run
>     in debug mode or not. In debug mode, extra information about
>     line numbers and local variables is emitted into the class files,
>     allowing for source level debugging and for stack traces with
>     line numbers. Setting the 'debug' variable will cause your JAR
>     files to be much larger, however. The default value for this
>     variable is 'true'.
>
>        debug=false
>
> thanks,
>
> bryan
>
>