[cross-project-issues-dev] Migrating from setProgramProperty to addProgr

[Stephan Herrmann <stephan@xxxxxxxxxxxxxxx>]

Hi,

I recently consumed the new touchpoint action addProgramProperty from [1]
and all seemed to work fine, but just as I'm doing final tests for our M6
contribution I noticed that this change breaks upgrading of our feature:

An error occurred while installing the items
session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=[R]org.eclipse.objectteams.otequinox 0.8.0.201101290806 --> [R]org.eclipse.objectteams.otequinox 0.8.0.201103151729, action=org.eclipse.equinox.internal.p2.engine.MissingAction).
No action found for: org.eclipse.equinox.p2.touchpoint.eclipse.addProgramProperty.
No action found for: org.eclipse.equinox.p2.touchpoint.eclipse.addProgramProperty.

In order to use the new touchpoint action users must already have M6 but
due to some dependencies they cannot update the SDK without also updating
our feature in the same step. I wasn't aware that the touchpoint action was
also performed during upgrade (maybe just because the action changed?).

Does anyone have some quick advice how we could avoid the not-yet-existent
touchpoint action from being performed when upgrading?
Otherwise I will have to revert to setProgramProperty for M6 and do the change
only in M7 (upgrading from M6 to M7 should then work fine).

thanks,
Stephan



[1] https://bugs.eclipse.org/329784 Touchpoint instruction for incremental changes to program properties