I encountered following problem during developing RCP application which uses P2 auto-update:
I have modified application launcher fragment (org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090 519). When I put modified plugin to repository, it is not updated during P2 auto-update process. Does someone know how to force this plugin to update programistically (without changing version)?
Paul Webster Messages: 6859 Registered: July 2009 Location: Ottawa
If you put the it in the repo with the same version number as the
previous fragment, it will never be updated. p2 considers a bundle with
the same version identical.
If you mean you want to ship a later version of that launcher fragment
to fix a problem you'd have to feature-patch the main containing
feature, where the feature-patch points to the new version of the fragment.