Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Patching a CDT plugin
Fragments make version upgrades very hard. We used to use fragments for platform patches and abandoned this approach in favor of building the whole Eclipse SDK ourselves.

-sergey


On Thu, Mar 6, 2014 at 7:24 PM, Guy Bonneau <guy.bonneau@xxxxxxxxxxxx> wrote:

I am developing a commercial plugin that use Eclipse’s CDT and need to patch 3 CDT plugins to fixe some issues I already reported on Bugzilla without which the usage of the plugin will fail.

 

I have reviewed the thread of Joseph Henry about the distribution of custom patches: https://dev.eclipse.org/mhonarc/lists/cdt-dev/msg26205.html . I have also read some info posted on Eclipse Wiki about how to use fragment to patch a plugin: https://wiki.eclipse.org/RAP/Patch_Fragments and https://wiki.eclipse.org/Steps_to_use_Fragments_to_patch_a_plug-in as I am struggling to choose a strategy for this.

 

Now regarding the strategy of using a fragment to patch a plugin. It is not clear to me if the manifest of the host plugin must be modified with the attribute Eclipse-ExtensibleAPI: true. If the Host Manifest need to be modified obviously I cannot ask an end user to do this. This would be an insane way to patch a plugin.

 

Can anyone shade some light regarding this?

 

Thanks

Guy


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top