tag:blogger.com,1999:blog-30049963.post2648899733533029265..comments2023-09-15T08:51:53.213-05:00Comments on Eclipse Lives In Winnipeg: Delivering Feature Patches - Part IIMichael Renniehttp://www.blogger.com/profile/11412892738963099114noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-30049963.post-56594937956854943102022-03-26T01:37:08.921-05:002022-03-26T01:37:08.921-05:00Some truly wonderful content on this web sit...Some truly wonderful content on this web site , thankyou for contribution. <a href="https://houstonembroideryservice.com/blog/custom-patches-for-jeans/?fbclid=IwAR2WAWb68OfGSjPkF-B4ThbNM7sZrNq_4-tLlQ41tHUhTTEZ2FChNWzSeHM" rel="nofollow">web page</a><br />kharizaffarhttps://www.blogger.com/profile/10557681565590381600noreply@blogger.comtag:blogger.com,1999:blog-30049963.post-1340338378024275592014-02-13T09:21:53.045-06:002014-02-13T09:21:53.045-06:00Hello,
I have managed to install the feature patc...Hello,<br /><br />I have managed to install the feature patch, (without changing the og.eclipse.cdt.debug.mi.core version), but the old plugin was not replaced by the new one. Any suggestions as to how I can fix this?<br /><br />ThanksmaybeNothttps://www.blogger.com/profile/02363031509787996460noreply@blogger.comtag:blogger.com,1999:blog-30049963.post-24630592625929719702014-02-13T06:21:11.018-06:002014-02-13T06:21:11.018-06:00Hello,
I am having some trouble installing a feat...Hello,<br /><br />I am having some trouble installing a feature patch. So I want to create a patch for org.eclipse.cdt.debug.mi.core plugin for eclipse SDK 4.2.2 (Juno sr2). I have imported the plugin in my workspace, made the necessary changes and also changed the patch version in the MANIFEST.MF file.<br /><br />I then created the Feature Patch for Feature ID: org.eclipse.cdt.gnu.debug and added the modified plugin in the Plug-ins tab. I then exported the Feature Patch using Deployable features and I have set the Options as explained in this tutorial. The corresponding feature and updated plugin jars were generated.<br /><br />The problem is when I try installing it via the Install New Software Option. I choose the feature jar file but I get the following message: "No software site(repository) found at jar". What am I doing wrong?<br /><br />I would also like to patch the org.eclipse.cdt.debug.mi.core.source in order to be able to make further modifications if needed. I was able to generate it when exporting the Feature Patch, but in order to patch it as well, should I create a second Feature Patch for Feature ID: org.eclipse.cdt.gnu.debug.source?<br /><br />ThanksmaybeNothttps://www.blogger.com/profile/02363031509787996460noreply@blogger.comtag:blogger.com,1999:blog-30049963.post-80333096722538140052008-12-05T10:47:00.000-06:002008-12-05T10:47:00.000-06:00Ian, in theory, yes importing as source would work...Ian, in theory, yes importing as source would work. If you can get the imported plugin to compile correctly, and the correct settings are in the build.properties file, PDE would treat your code the same as it would if it were grabbed via CVS. The problem is that importing doesn't always get everything perfectly right, but we do our best :)<BR/><BR/>Sud, feature patches are used to replace parts of the code in an existing feature. Fragments can be used to provide custom implementations of libraries in plug-ins (which may or may not be part of a feature). Fragments are for providing multiple implementations (for each OS for example), not for modifying existing code.<BR/><BR/>Emilien, everything in p2 has 'required capabilities' that define what it needs and what it can work with. p2 does its best to install/update each piece in a way that completely satisfies every required capability. It is easy to try and install something that can't be completely satisfied, resulting in your "Cannot find..." problem. The only way to avoid it, is to make sure the features you are working with are using the correct version. Features, at least in the SDK, have a specific version, and have requirements on specific versions of bundles (vs bundles which can easily define version ranges). So it is easy to have the incorrect version when working with features. Sorry that this isn't much help, p2 is working towards better problem reporting.Curtishttps://www.blogger.com/profile/07823163562402913233noreply@blogger.comtag:blogger.com,1999:blog-30049963.post-77296918042241457542008-12-05T04:30:00.000-06:002008-12-05T04:30:00.000-06:00Great tutorial !About your question sud: You need ...Great tutorial !<BR/>About your question sud: You need to create a Feature Patch when you want to install the feature throw p2 which is already installed in your bundle, such as an update.<BR/><BR/>I have a question too:<BR/>The patch enables to avoid the error message "Cannot find a solution where both Match" with p2 installation. Is there a way to avoid this message when you try to update an existing feature with the update button ? Thanksemilienhttps://www.blogger.com/profile/06340896471670366325noreply@blogger.comtag:blogger.com,1999:blog-30049963.post-51608017663405251352008-12-04T17:56:00.000-06:002008-12-04T17:56:00.000-06:00How is this different from the currently available...How is this different from the currently available "New Plug-in Fragment" project creation wizard.sudhttps://www.blogger.com/profile/13628606966401327565noreply@blogger.comtag:blogger.com,1999:blog-30049963.post-51464426893905905992008-12-04T17:02:00.000-06:002008-12-04T17:02:00.000-06:00One think you missed is where you got the source f...One think you missed is where you got the source from. Does this have to come from CVS (or something that supports "creating a patch" from), or can I import bundles (with source) from my target?Ian Bullhttps://www.blogger.com/profile/02668098567506210626noreply@blogger.com