Re: Scanning Project Classpaths

Steve Frechette wrote:
> Frequently during a debug session, JSwat become busy whiole it is =

> =93Scanning Project Classpaths=94. Although I have a large number of =

> classpaths listed, it can take over a minute for JSwat to resume.

Is this task occurring in the background, or is it preventing you from =

operating JSwat normally? Older versions of JSwat would run the task in =

the foreground, blocking you from doing anything else, but the newer =

versions do not have this problem.

> Is this normal behavior? Why does it occur frequently during the session =

> even though I have not changed my list of classes since installing? Is =

> there an optimization for this?

The most recent versions have a checkbox when connecting to a debuggee =

that allows you to ignore the debuggee classpath. That may help reduce =

the amount of scanning that occurs. In general, the scan is supposed to =

cache the results and only do a quick scan for subsequent changes.

> Should I report this as a bug?

You can do whatever you feel is right.

n