My RCP-Self-Update is not working


Not sure how many people have been running into this problem but because it happened to one of my coworkers today I thought I should blog about it.

The problem was the following: We added the p2-update possibility to an application at the end of our product development like it is shown in the cloud example found in rt-CVS, we correctly added the p2.inf-File and exported the application but die Update did succeeded because there’ve been no repositories configured when the application was exported.

It took us some time to figure out what he did wrong and the solution though obvious, logic and simple is something others could easily miss also when exporting from the Eclipse IDE.

We forgot to check the “Generate metadata repository”

Like I said: Obvious, logic and simple to fix but my coworked nearly gave up. So should the export wizard when finding a p2.inf in the project not at least warn if the “Generate metadata repository” is not checked?

Advertisements
This entry was posted in Eclipse. Bookmark the permalink.

One Response to My RCP-Self-Update is not working

  1. Dave Orme says:

    I’ve been bitten by this too. Also, if you fail to check this box, the resulting application isn’t updateable at all.

    I agree that there should at least be a warning if you fail to check this box. It seems that the explanatory text next to the checkbox could be better.

    Dave Orme

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s