[news.eclipse.tools] Re: Debugging under VA Java

["Jeff McAffer" <jeff_mcaffer@xxxxxxx>]

Rick

This is a great topic.  So great that I will not answer here :-)  I have
started a new thread because this is important for everyone to see.  Check
out the post entitled
    "Of interest to all: .va.properties vs. plugin.jars"
Hopefully that will answer most of your immediate questions.

Jeff

"Rick Stevens" <rstevens@xxxxxxxxxx> wrote in message
news:9bhtdu$atf$1@xxxxxxxxxxxxxxxx
> Looks like a missing .va.properties was the problem. Once I created one in
> my plugin directory, I was able to debug my plugin code just fine. This is
> the first time I've heard of .va.properties. Could someone elaborate on
> it's purpose? It appears as though projects identified in .va.properties
> are searched for classes to load/debug and, if the class in question is
> not found, then the the items in the <library> section of my plugin.xml
> are used to load the class. Is that a correct interpretation?
>
>
> Gary Karasiuk wrote:
>
> > Do you have your .va.properties set for the plugin that you are trying
to
> > debug?
>
>
>
>
>