What's the distinction between a release and debug build in this case? >From the point of view of the federated build and the classlib build, that is. Is release the default?
One concern is the loss of line numbers from stack information; is that lost too? My other thought is that ALL of our builds are still "debug", including our milestones. That may just be my opinion though. I'm not too worried about, just weighing in. -Nathan On Mon, Mar 3, 2008 at 3:58 AM, Pavel Pervov <[EMAIL PROTECTED]> wrote: > Nathan, > > The patch is not in yet. > The idea of debugging release build of class library looks somewhat > peculiar to me. > > Do I miss some scenario here? > > Should we introduce build switch to make it possible to add LVT > information to release if required? > > Pavel. > > > > On 3/1/08, Nathan Beyer <[EMAIL PROTECTED]> wrote: > > It may be too late, but I vote -1 on this change. 1.5M reduction > > doesn't offset the loss of no longer seeing the local variables during > > debug. > > > > -Nathan > > > > On Thu, Feb 28, 2008 at 3:08 PM, Gregory Shimansky > > <[EMAIL PROTECTED]> wrote: > > > Alexey Petrenko said the following on 28.02.2008 16:52: > > > > > > > Will Eclipse debug work with the release build of Harmony in this case? > > > > > > It will but with absence of local variable tables it probably won't show > > > local variables in context. > > > > > > > > > > 2008/2/28, Pavel Pervov <[EMAIL PROTECTED]>: > > > >> I would like to propose the following improvement to class library > > > >> build - build in release with only line number information in .class > > > >> files. > > > >> > > > >> It saves ~1.5MB in jre size. > > > >> > > > >> If no objections then I'll commit HARMONY-5558. > > > >> > > > >> P.S. The patch in that JIRA introduces switchable compression for > jar > > > >> files containing class library classes. Default mode is kept > > > >> compressed. > > > > > > > > > -- > > > Gregory > > > > > > > > > > > -- > Pavel Pervov, > Intel Enterprise Solutions Software Division >
