|Problem mirroring a p2 repository [message #1810345]
||Thu, 08 August 2019 14:55
| Nils Loose
Registered: September 2017
we're developing an eclipse/equinox based RCP application, that is updated from a p2 repository. We want to mirror that repository as described in the Developers Guide. When we did this the last time in december/january it worked perfectly. In the meantime we migrated our application to the new eclipse version (2018-09 back then, 2019-06 now), and now when trying to mirror our repo we get the following error message:
java.lang.RuntimeException: Application "org.eclipse.equinox.p2.metadata.repository.mirrorApplication" could not be found in the registry.
Same for the artifact repository. Obviously, the mirror application seems to be missing. Now according to the Developers Guide, for mirroring reopsitories "you simply need an eclipse installation that contains the org.eclipse.equinox.p2.artifact/metadata.repository bundle". This condition should be fulfilled, as our application includes the org.eclipse.equinox.p2.core.feature that contains those bundles, and jar files for both bundles are located in the application's plugins folder. I think that should be sufficient to make the mirror tool available, or am I overlooking something?
As initially mentioned, it worked three eclipse versions ago. Have there been any changes to p2 in the meantime that might explain why it no longer does?
Any other ideas what I'm doing wrong here? Any help would be appreciated! Thanks in advance!
|Re: Problem mirroring a p2 repository [message #1810425 is a reply to message #1810345]
||Sat, 10 August 2019 15:38
| Christian Derksen
Registered: September 2017
I worked on the problem as Nils and we - somehow - figured out, how to reattach the repository mirroring to our product.|
After also checking via OSGI console the states of the p2 bundles, we found that these bundles were loaded in the same way as for an eclipse IDE. But still we got the error that org.eclipse.equinox.p2.metadata.repository.mirrorApplication could not be found in the registry, if we tried to start the mirroring using the command line options.
In the past, the only two bundles that we added to the dependencies of our core product bundle were:
and that seems to do the job but fails now as described.
Checking the tutorial of Lars and adding some further bundle dependencies to our products core bundle, we end up with the following p2 dependency configuration:
Here, the bundles 1, 2, 4 and 5 came from the mentioned tutorial, Bundle 3 worked in the past and we simply let it as is, 7-9 are required and used by the SWT workbench and properties window.
Finally, Bundle no. 6, I guess, did the trick to let products mirror repositories via command line.
[Updated on: Sat, 10 August 2019 15:38]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02091 seconds