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

Bug 323321

Summary:	[director] Why do set change the value of roaming
Product:	[Eclipse Project] Equinox	Reporter:	Pascal Rapicault <pascal>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	john.arthorne, thomas
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:	stalebug

Description Pascal Rapicault

2010-08-21 21:49:47 EDT

While investigating the issues related to the shared install, I noticed that whenever we run perform a provisioning operation using the director app, we unset then reset the roaming flag. 
This feels pretty much like something that we use to need when we did not had the concept of Agent, but now this seems unnecessary.

Comment 1 Pascal Rapicault

2010-08-21 21:50:17 EDT

Thomas, John, does that ring a bell?

Comment 2 Thomas Hallgren

2010-08-23 08:28:30 EDT

Yes, I think that code was needed when the director was run in context of something larger (such as the IDE). If it can run 'stand-alone', i.e. with an agent of its own, as opposed to the default agent used by the IDE, then I don't think this is needed anymore. Question is, does it use it's own agent now?

Comment 3 John Arthorne

2010-08-24 16:06:48 EDT

See bug 269468 comment 50 from DJ. If I understand it correctly, this was only a problem in the single agent world where we were provisioning a profile with the same id as the currently running system, but in another location. I.e., using a director call inside one SDK to provision into another instance of the SDK.

Comment 4 Eclipse Genie

2019-04-15 16:00:07 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.

Comment 5 Lars Vogel

2019-10-29 05:33:36 EDT

This bug is marked as stale for some time. If it is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.