[news.eclipse.newcomer] Re: Separate output for debug info?

[Jeff <jlar310@xxxxxxxxx>]

Nick Boldt wrote:
> How about using two ant scripts to build & deploy -- one with debug on, 
> the other with it off? Then, using the Ant view, you can just 
> double-click the appropriate script (or target within a script, if you 
> want to get fancy) and you'll build w/ or w/o debug.
>
> Jeff wrote:
> > I do not want to deploy my java class files with debug info. But it is 
> > cumbersome to turn off debug info, rebuild, then deploy. Not to mention 
> > remembering to do so.
> >
> > Is there anyway for Eclipse to maintain two output folders, one with 
> > debug info, one without?

Ant is problematic as you have to manually configure (again) your 
classpath and libraries.

I have, however, found an acceptable solution:

Create a secondary project with a "Linked Source" folder to the 
main project. Configure project specific compiler settings to 
include debug info. Then it's just a matter of having the run 
configurations pointing to the secondary project.

Oddly enough, when I created my 'debug' project, I named it 
[main-project-name]-debug and the project automagically had 
debugging info enabled in the compiler. It seems the Eclipse 
developers have created an undocumented solution!

Jeff