[cdt-dev] Quadruple Thank You

[Keithen Hayenga <keithen@xxxxxxxxx>]

I want to thank Mikhail, Leo, and (i am sorry to say i have forgotten the name of) the third of the managed build team of presenters at the CDT BOF at EclipseCon. Your letting me know about the -clean option immediately got me past one roadblock in building my plug-in. And Leo and Mikhail putting me on to refresh got it so that pressing finish for the new managed make C project now results in a project with sources fully built; ready to run and debug. 

I was left with the last problem of this working in the runtime Eclipse, but not our main Eclipse. Thank you Wieant for the pointer to the debugging info that is now bookmarked in my browsers. It did arrive after i had riddled Eclipse with System.out.printlns and solved my problem. (My heavy handed tracing did reveal a minor bug that the runtime guys have already rolled a fix for into 3.2.) I had used the .metadata/.log to find out that Eclipse was trying to instantiate a class that i had removed from my plug-in and which i could no longer find referenced anywhere in the plug-in. I wound up creating a new plug-in where i kept the same structure and code, but renamed the classes and was consistent about only using the new names in the new plug-in. It worked perfectly the very first time i tried it out in both Eclipse executables.

Thanks again everyone.

-Keithen

-----Original Message-----

From: Wieant Nielander [mailto:wieant@xxxxxxxxx]

Sent: Friday, March 31, 2006 4:52 AM

To: CDT General developers list.

Cc: Keithen Hayenga

Subject: Re: [cdt-dev] Difference between main Eclipse plug-ins and

runtime version

Keithen,

Not sure if you already fixed the issue, but we have ran into a similar

situation. First of all I'm not sure if simply copying the entire plugin

project automatically works. Within the PDE the java modules are

generally

compiled into a 'bin' subdirectory, and if you use a straight copy the

classloader might not look there?

Apart from that you could try to trace all the classes being loaded from

your 'standalone' situation, the following link was very helpfull

in that respect:

http://www-128.ibm.com/developerworks/rational/library/06/0221_rossner/

For example, using the following 'build.options':

------------------------------------------

org.eclipse.osgi/debug=true

org.eclipse.osgi/debug/loader=true

org.eclipse.osgi/trace/classLoading=true

org.eclipse.osgi/trace/activation=true

------------------------------------------

and the following command line call:

  java.exe -cp startup.jar org.eclipse.core.launcher.Main -debug

build.options

allows you to see exactly which classes are being loaded, and if

loading some of them might fail.

Regards,

  Wieant

Message: 4

Date: Wed, 29 Mar 2006 11:46:18 +0400

From: "Sennikovsky, Mikhail" <mikhail.sennikovsky@xxxxxxxxx>

Subject: RE: [cdt-dev] Difference between main Eclipse plug-ins and

runtimeversion

To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>

Message-ID: <AFFB534DFDE16E44B5413E9F8B8E2AD201A62DF9@NNSMSX401>

Content-Type: text/plain; charset="us-ascii"

Try launching ecilipse with the -clean option specified after you add

your plug-ins to eclipse. That'll force eclipse to clean the extension

registry data and reparse the plug-in information.

Regards,

Mikhail

________________________________