Re: [cross-project-issues-dev] Patch application is broken in Kepler SR1
Thanks for the tip! The patch scope is not set to a range in our repository
Since the issue is still not fixed in p2 (seriously!?), what did you do for
a workaround in your patches?
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Carsten
Sent: Tuesday, September 17, 2013 11:40 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Patch application is broken in
We are doing something similar with patches in our product. I just did a few
quick tests and everything seems to work as expected for me with Kepler SR1
RC3. With a feature installed in a different version than targeted by our
patch - both higher or lower - the patch is rejected.
On 17.09.2013 19:36, Konstantin Komissarchik wrote:
> In Juno and prior, if a patch doesn't apply, there would be an error
> in p2 ui and user can deselect the patch. In Kepler, the patch is
> installed, despite the fact that it is for a version of the feature
> that doesn't exist in the target.
We had a similar problem in the past, but that was way back when (I think
Indigo). It was caused by the P2 publisher not creating the proper version
bounds for the patch feature in the repository metadata.
Given that you are only hit now, this is probably not the problem, but it
doesn't hurt to check. Make sure that the <patchScope> version range in your
content.jar/content.xml has the expected value, e.g.:
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=350088 for the
long-standing bug on this.
> Is this related to the p2 problem solving abilities added in Kepler?
> If so, is there a way to turn that off? Any other ideas on how to get
> patches working properly in Kepler?
If remediation gets involved, you should see a page in the wizard that
outlines the changes to your installation (e.g. I got that when trying to
apply a Kepler patch to an older feature from Juno, suggesting an update of
the patched feature for the patch to apply).
cross-project-issues-dev mailing list