I took the org.eclipse.equinox.p2.examples.rcp.prestartupdate project and adapted it for use in my RCP application. Then I install the update repository, which updates as part of my nightly build.
When I open my application, it goes through such movements as it updates - it finds the update site, correctly installs and installs the operand for each package and says that it ended without errors. The problem is that plugins are never installed in the plugins folder, even though the profile is updated (there are no updates in future versions of the launch). The next time my build launches it, it will correctly identify for updates, but the same thing happens again.
I debugged the days, and the only thing that looks unusual (not that I fully understand what is happening) is that during the last setup phase, none of the TouchpointData objects have any instructions, so it doesn't look like configure does what should.
I have no idea where to look further and would like to see if anyone has any ideas.
Update:
Finally, I realized what was going on.
The problem started when I built my product without creating a metadata repository. When creating through Eclipse, I did not check the "Generate metadata repository" in the export product wizards, because I do not need the p2 repository, just a product. The problem is that without checking this button, the product does not install with P2 turned on, causing side effects such as a lack of profile among other things.
, , , . , .
"Generate metadata repository", , .
, , , , , , . Hudson , , Eclipse Export Product, . , - .
, PDE?
. , , , , . , . , , org.eclipse.equinox.executable -. , . , .