RE: Classpath problem

Nathan,

Your nightly build fix works perfectly!  Thanks for doing this.

One quick follow-on question: I got your newest code by downloading the
nightly installer.jar, extracting jswat.zip, and hand-copying the newest
files on top of my current installation.  I did it this way because I
wasn't sure whether the new installer would reset any of my current
environment settings.  (Since I've spent the last couple of days getting
JSwat configured the way I like it, I didn't want to lose any settings.)

So, is it safe to run future nightly-build installers without having to
worry about losing any of my current settings?

Thanks again.

Jay

-----Original Message-----
From: Nathan Fiedler [mailto:[email protected]]=20
Sent: Monday, May 01, 2006 10:55 AM
To: Burgess, Jay S
Cc: [email protected]
Subject: Re: [jswat-user] Classpath problem

The annotations have tooltips, so if you hover the mouse over the red=20
icon in the source view margin, it should indicate what it thinks the=20
problem is.

In the meantime, the nightly build contains a recent change in which the

Attach dialog allows you to ignore the classpath reported by the=20
debuggee. So you can set the "Classes" setting however you like, attach=20
to the remote debuggee, and the Classes value will remain the same. The=20
nightly build is available on the downloads page at bluemarsh.com.

On the other hand, turning off the annotation certainly works. The=20
errors in JSwat are meaningless since it is not compiling anything and=20
is not intended to be used as an editor, so you wouldn't care about the=20
errors in any case.

n


Burgess, Jay S wrote:
> Your description of the change in classpath before/after Attach makes
> sense. But your statement that "everything that is on the sourcepath
> will not generate error stripes." doesn't seem to align with what I'm
> seeing in the tool.  In lieu of a screenshot, since I'm not sure what
my
> boss would think about that, I'll try to describe it more clearly in
> words:
>=20
> -----------------------------------
> Before Attach:=20
> -----------------------------------
> * The "Session Settings/Classes" tab contains the root directory of my
> application's class files.=20
> * The "Session Settings/Sources" tab contains the root directory of my
> application's source files. =20
> * An import statement in one of my source files that imports another
one
> of my app's classes has NO red wavy line e.g. In
> "com.mycompany.report.Top10.java", the line "import
> com.mycompany.beans.Channel;" has no red wavy line.
> * I can see both "com.mycompany.report.Top10.java" and
> "com.mycompany.beans.Channel.java" in my Sources tab and open both
files
> in the editor.
>=20
> -----------------------------------
> After Attach:
> -----------------------------------
> * The "Session Settings/Classes" tab now contains just tools.jar and
> bootstrap.jar, and my previous setting is gone. (This aligns with what
> you said about the debuggee.)
> * The "Session Settings/Sources" tab contains the root directory of my
> application's source files (as it did previously).
> * The previous line of source in JSwat that references one of my app's
> classes NOW HAS a red wavy line!
> * I can still see both files in my Sources tab and open them in the
> editor.
>=20
> Again, this isn't a huge deal, and I can turn off the red wavy line in
> Annotation Types.  I just wanted to make sure I wasn't missing
> something.
>=20
> Jay