Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334670

Summary:	[reconciler] Determine if ProfileSynchronizer.synchronize() needs explicit way to invoke setProfileStateProperty API
Product:	[Eclipse Project] Equinox	Reporter:	Dean Roberts <dean.t.roberts>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	dj.houghton, jeffmcaffer, john.arthorne, pascal
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Dean Roberts

2011-01-18 11:33:17 EST

Build Identifier: 

With the completion of Bug 323888 ProfileSynchronizer.synchronize() has the opportunity to tag a profile state with metadata so that it is hidden in the InstallationHistory view.

However, the implementation in that bug takes advantage of non speced behaviour to get handle on the new profile state by calling profile.getTimestamp()on the profile that the ProfileSynchronizer instance is holding onto.

A determination needs to be made as to whether we can spec the behaviour of updating the profile timestamp OR if we need to introduce some new mechanism involving IStatus so that applyConfiguration() can return the new profile state as part of the return value.



Reproducible: Always

Comment 1 Eclipse Genie

2019-06-25 16:37:49 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.