| Re: [cdt-dev] Distribution of custom patches. |
|
We actually fork the CDT for our post Juno SR-2 changes. We clone the repo and make our local changes on a branch. We then build the CDT's p2 repo using Maven. And that feed that into the rest of our product build chain. As long as you change the qualifier
so it's after the CDT's (e.g. prefix them with a letter), you should be able to get your users to point their Eclipse at that repo to get your version.
Patching jar files is probably not the right way to do that.
Doug.
From: Joseph Henry <Joseph.Henry@xxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx> Date: Monday, 15 July, 2013 3:59 PM To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx> Subject: [cdt-dev] Distribution of custom patches. Hi all, My company has a custom Eclipse CDT integration for our development environment. We are using Eclipse Juno with CDT version 8.1.2. We recently encountered 2 core CDT bugs (408525,
407506) which block usage of our plugin.
We have internally patched the associated CDT jars for 8.1.2, but I need a way to easily distribute them throughout our company. Right now we are just naming the jars the same and telling users that they need to download the jar and copy
it to there eclipse directory. This is quite cumbersome, and with over 300 users, it is a bit of a support nightmare. I was wondering if anyone knew of a way to distribute these patched jars via a feature update site? I have tried building the jars and making my plugin distribute them, but eclipse wont accept the jar if it is already in the plugin folder with the same name, and if the name is different, the CDT does not recognize it. |