All geek questions in one place

Is the Site Update Wizard PDE still the right way to create an update site?

The purpose of this question is to get confirmation from someone who knows about the current state of affairs with the Eclipse installation system.

I have an Eclipse plugin and I want to create an update site for it using the simplest (but correct) method. My initial impression was that I:

  • Create a function using the Feature PDE project.
  • Add my plugin to this feature.
  • Create an update site with a draft PDE update site.
  • Add my feature to the update site.

Then I started looking for documentation throughout the Eclipse installation system and started reading about this P2 thing, which is apparently new and replaces everything that was before.

The information I find about PDE projects and wizards does not discuss P2, or I did not find the right information, which makes me a little nervous that I can do something wrong or something important.

So, I need to take care of P2 or P2 something that happens under the hood, where can I safely ignore it while I continue to use PDE tools?

Thanks!

+6
source share
1 answer

No, everything is in order, P2 is no longer new. It was introduced in Eclipse 3.4 several years ago, replacing the old update manager. IBM has an article about it here .

As is often the case with Eclipse concepts, Lars Vogel has a good tutorial on this subject at http://www.vogella.de/ .

By the way, an even simpler way to create an update site is not to create an update site project, but instead export this function as a deployment function. The same files are created. But it’s better to create an update site project, especially if you will make frequent releases.

+4
source

Source: https://habr.com/ru/post/898770/

More articles:


All Articles