[news.eclipse.newcomer] Re: Plugin Fragment & External Jars

["Walter Harley" <wharley@xxxxxxx>]

"George Karabotsos" <g_karab@xxxxxxxxxxxxxxx> wrote in message 
news:epfvsh$c9b$1@xxxxxxxxxxxxxxxxxxxx
> I am glad to hear!  Yes Java problem markers is in my lists of tasks to 
> do.  Is there any tutorial or guide for doing so?

There are no tutorials or guides for using CompilationParticipant, but you 
can look at the code in org.eclipse.jdt.apt.core for examples.


> OK thanks for pointing out this fact - I am wondering, however, whether 
> its possible to create Java problem markers with builders?

I'm hazy on the details of that.  My vague understanding is that a builder 
can contribute its own markers but it cannot literally contribute Java 
problem markers; that is, the builder's markers would show up separately in 
the Problems pane.  That may be the best thing anyway.

But I may be wrong about that.


> Thanks you Walter!  This solved my problems!  Again on a related note, 
> when you develop a plugin how you have setup your environment?  Right now 
> I am just exporting my plugin in the .../eclipse/plugins directory and I 
> restart the tool.  It is satisfactory, but I am wondering what other 
> people are doing.

If you don't already have it, I would strongly suggest finding a copy of 
"Eclipse: Building Commercial Quality Plug-ins", 2ed., information here: 
http://www.qualityeclipse.com/.  I found it invaluable in learning how to 
work with plug-ins.

I have a workspace that contains my plug-in project, as well as the imported 
code for any Eclipse plug-ins that I'm interested in debugging into.  Then, 
in order to test or debug, I launch a target instance of Eclipse using 
"Run/Debug As..." -> "Eclipse Application".  That way it's not necessary to 
actually export the plug-in; PDE (the Plug-in Development Environment) takes 
care of all the necessary steps under the covers.

Often, if testing my plug-in requires constructing a bunch of sample code, I 
will set up my launch configuration to point to a specific target workspace; 
so, I might have "myplugin-host" as a workspace that contains my plug-in's 
code, with a launch configuration that specifies the location of a second 
workspace, "myplugin-target", that contains the sample code needed for 
testing.