[aliant_mwalker]

Doing builds against a ClearCase view (run externally using ClearCase Remote Client standalone eclipsed based tool), the MyEclipse Build takes between 5 and 10 minutes. Not sure why, but doing an external build with ant outside of eclipse takes under 30 seconds. (Note: Same script in MyEclipse takes same long amount of time).

My question is, what switch do I need to set on my build options that will allow my externally built packages to work with MyEclipse debugging for servlets. -g does not appear to work. Not even sure if it is supported, but would be very nice if we could get speed of external build and still be able to debug in eclipse.

Any help, comments or suggestions would be greatly appreciated! ❓

Mark W.

[Riyad Kalla]

Mark,
You’ll want to edit your javac task per the documentation here:
http://ant.apache.org/manual/CoreTasks/javac.html

to enable debug, it’s something like:

<javac debug="true" debuglevel="lines,vars,source"></javac>

double check me though.

[aliant_mwalker]

I tried to do that but it does not work. Could it be the fact that I am (required) to use jdk 1.3.1_18 (due to the version of Oracle 9iAS in prod).

Or is there something or somewhere I have to put the code after it has been built in order for MyEclipse to be able to see it to step through it.

Mark W.

[Riyad Kalla]

Ahh yes that will likely do it, our debugging is based around the JSR-45 specification which you must be using a JVM 1.4+ to utilize, I believe the same would hold true for the byte code that was generated.

[aliant_mwalker]

T hat’s what I was afraid of. I will try to see if the java compiler target switch (change from 1.3 to 1.4 will work but it will only help with debugging logic and not library type errors.

Thanks for your time.

Mark W.

[Author]

Posts