[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] best practices for patching the eclipse IDE?

If you are running 3.5, and you are running the version of the platform you intend to patch then exporting the plug-in into the running install is the best way to try things out.
As for the bug report I think you want to refer to https://bugs.eclipse.org/bugs/show_bug.cgi?id=271022 

Inactive hide details for "Jon Barrilleaux" ---04/06/2009 03:04:39 PM---I started a thread over on the platform newsgroup in th"Jon Barrilleaux" ---04/06/2009 03:04:39 PM---I started a thread over on the platform newsgroup in this regard (eclipse.platform, "how to create a


From:

"Jon Barrilleaux" <jonb@xxxxxxxxxxxxxx>

To:

<p2-dev@xxxxxxxxxxx>

Date:

04/06/2009 03:04 PM

Subject:

[p2-dev] best practices for patching the eclipse IDE?




I started a thread over on the platform newsgroup in this regard (eclipse.platform, “how to create and install a feature patch”). Francis Upton suggested I post here. Essentially, I have submitted a bug and developed a patch to the Java code formatter. Now I want to try it out on a clean version of the Eclipse IDE. What are the best practices for doing this?

The available documentation is spotty at best, and so far doing a feature Patch is not working (Paul Webster is currently working with me on it via the newsgroup). Ideally, I would like to do something like a plugin fragment to patch one or more platform plugins, which would then be incorporated into a feature patch. However, the documentation for plugin fragments indicates that this is not what they are intended for since loading order cannot be guaranteed (or something like that). So, for now, I am simply trying to replace the whole plugin (org.eclipse.jdt.core) via a feature patch.

In any case, the issue of how to patch the eclipse platform is a real one, especially if mere mortals are intended to contribute to the platform (they should be able to easily test their patches first, which does not seem to be the case). Also, there seem to be a number of “issues” in the existing 3.5 p2 update manager. I have begun to note these in bug 27102.

--jon


CONFIDENTIALITY NOTICE: This electronic mail message and any attachment hereto may contain confidential information of Meyer Sound Laboratories, Incorporated and is intended for the personal and confidential use of the designated recipient(s) only. If you are not the intended recipient (or responsible for delivering the message to the intended recipient), you have received this message in error and any review, distribution, or copying of this message or any attachment hereto is prohibited. If you have received this message in error, please promptly notify the sender and permanently delete it from your computer.
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

GIF image

GIF image