You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Thorsten Scherler <th...@apache.org> on 2005/09/25 16:13:31 UTC
[Proposal] Adding @debuglevel to the compile-build.xml
Hi all,
in forrest we run lately into problems with the linkrewriter and jxpath.
I am trying to debug that but I had some problems.
The problem I had in debugging the
org.apache.cocoon.transformation.LinkRewriterTransformer class in
eclipse (3.1) for forrest is that I got:
"Unable to install breakpoint in ... due to missing line number
attributes. Modify compiler options to generate line number attributes.
Reason: Absent line number information"
See
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-7304.html for a
similar problem.
I patched cocoons compile-build.xml like:
Index: compile-build.xml
===================================================================
--- compile-build.xml (revisiĆ³n: 291352)
+++ compile-build.xml (copia de trabajo)
@@ -24,6 +24,7 @@
<!-- compilation parts used by all targets -->
<presetdef name="cocoon.javac">
<javac
+ debuglevel="lines,vars,source"
debug="${compiler.debug}"
optimize="${compiler.optimize}"
deprecation="${compiler.deprecation}"
wich was recommended in the link.
I compiled cocoon again and then copied the linkrewriter block lib to
the core of forrest and could connect to the class to debug.
The @debuglevel is only taken into account if the debug="true" so IMO it
is not doing any harm if we add it. On the other hand with this
attribute set we can debug cocoon with eclipse again.
WDYT?
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)