Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Re: Re: questions about building and modifying CDT plugins

> 0. If I replace the original
> org.eclipse.cdt.make.core_6.0.0.201002161416.jar with one
> built/exported
> from the source project, I can run the target eclipse CDT
> installation with
> no errors. (No plugin-loading errors in the Error Log View)
> This is expected
> as I should have made no changes.

That's the way I patched my CDT with a bugfix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=271623

> 1. If I bump the build# (the x in 6.0.0.x) in the plugin.xml for
> org.eclipse.cdt.make.core, and build/export it into the target CDT
> installation so that there are now 2
> org.eclipse.cdt.make.core* in plugins/,
> I get no plugin-loading errors, but when I look at About Eclipse -
> Installation Details - Plug-ins - I see that the old
> org.eclipse.cdt.make.core was loaded, not the new one. From
> this, I infer
> that for a given plug-in name, Eclipse will dynamically load the first
> plug-in it finds with that name (alphabetically?) and not
> reload it when it
> finds other identically named ones. Is this correct?

Just copying a plugin with a new version won't work. The eclipse plattform keeps track of the jars to use. AFAIK, you have to create a new deployable feature version and update eclipse with the new one. To much work for me -> I prefer #1 ;)

> 2. If I delete all org.eclipse.cdt.make.core plug-ins and
> then export the
> org.eclipse.cdt.make.core with the bumped version number so
> that it is the
> only org.eclipse.cdt.make.core* in plugins/, I see a plug-in error for
> org.eclipse.cdt.core in the Error Log when I run the target
> eclipse CDT
> installation: "Error: required build system is not installed"
> When I look in
> About Eclipse at the list of loaded plug-ins, I do not see
> org.eclipse.cdt.make.core in there. Presumably, there is
> something wrong
> with the plug-in that I just built and exported, even though
> the only change
> I made to it was to bump the version build# from 6.0.0.201002161416 to
> 6.0.0.201002161417. Any idea what I might have done wrong?

See my comment above.

--Harald


Back to the top