Hello again,
I'm a long-time emacs guy for development, but I'm using GeoNetwork as
my excuse to learn to use Eclipse. Heck, Jeroen uses it and that's good
enough for me.
Part of the rationale for the preceeding message, related to building GN
under Fedora Core 8, was motivated by a problem I've been having with
running GeoNetwork in the Java debugger inside Eclipse under Windows. I
was hoping the problem was Windows-specific and that moving over to
Linux would solve the problem, but it doesn't.
I'm asking for help here because of the way GeoNetwork runs via Jetty,
and perhaps some of you may already have solved the problem. It seems
more GeoNetwork-specific than Eclipse related.
Here's the story - I can compile GeoNetwork just fine inside of Eclipse.
I can run it fine there, as well. However, if I try to start it in the
debugger, I get an error message (both on Windows and on Linux) saying
"Cannot connect to VM" and "socket closed" and all I get is a usage message:
Usage: java [-DDEBUG] [-DSTART=start.config] [-Dmain.class=org.MyMain]
-jar start.jar [--help] [config ...]
This happens with both Eclipse 3.2 and 3.3 and, as I said, on both Linux
and Windows.
Have any of you encountered this and, if so, how did you fix it? Am I
missing something fundamental (which is likely!) in trying to configure
Eclipse to run GN in the debugger, given that it runs without the
debugger just fine inside Eclipse? If you're not using the Eclipse
debugger, how are you debugging your GeoNetwork developments? Right
now, I'm embedding statements to print stuff to the log, but that feels
so 1970s...
Thanks in advance.
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.