Re: Callstacks in jenkins-built apps without line numbers
Re: Callstacks in jenkins-built apps without line numbers
- Subject: Re: Callstacks in jenkins-built apps without line numbers
- From: Johann Werner <email@hidden>
- Date: Wed, 26 Sep 2012 16:10:55 +0200
| Hi Maik,
congrats to mastering jenkins :)
To have more info in your stack traces you have to disable optimization during the compilation. Check your wocompile ant task:
<wocompile destdir="bin" source="${compiler.source}" target="${compiler.target}"
deprecation="${compile.deprecation}" debug="on" optimize="off"
encoding="utf8" includeantruntime="false">
Important is to add the optimize=off otherwise the reported line numbers can differ from your source code line numbers.
jw
Hi,
I recently started using Jenkins for my builds. Due to our complicated structure of Wonder, company-specific generic frameworks and project-specific frameworks with all sorts of interdependencies, it took a lot of build.xml tweaking, ERJenkins changes and stuff, but now the first Jenkins-built release is running in production.
The only thing that bugs me is if the app throws an exception, the callstack has lines like this:
com.selbstdenker.foo.Bar.myMethod(Unknown Source)
whereas previously it was:
com.selbstdenker.foo.Bar.myMethod(Bar.java:123)
What could have caused that information to be not contained any more in the builds?
Thanks
Maik |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden