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

Bug 334810

Summary:	Inconsistent enablement for Share Project... menu item with multi-selection
Product:	[Eclipse Project] Platform	Reporter:	Ishfak Bhagat <bishfak>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	a.gurov, bishfak
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Ishfak Bhagat

2011-01-19 11:37:28 EST

Build Identifier: SVN 0.7.8

Have seen inconsistent enablement for Team / Share Project... menu. 



Reproducible: Always

Steps to Reproduce:
1. On a new Eclipse launch - Multi-select 2 projects
2. Right-click, and select Team from the context menu
3. See that 'Share Project...' is disabled (it is enabled for a single selection)
4. Create/Open some project
5. Switch to Navigator or Package Explorer view
6. Multi-select the projects again
7. Right-click, and select Team from the context menu
Now see that 'Share Project...' is enabled

Unclear whether Share Project... should be enabled or disabled for multi-selection, but should be consistent.

Comment 1 Alexander Gurov

2011-01-19 14:28:11 EST

Actually, version control system plug-ins are not related to management of the "Share Project..." action enablement, which is еру "Team" component responsibility. So, having no way to fix the described issue I will move this bug report to the "Team" component of the "Platform" product.

Comment 2 Tomasz Zarna

2011-01-20 05:36:55 EST

(In reply to comment #0)

> Steps to Reproduce:
> 1. On a new Eclipse launch - Multi-select 2 projects

In what view did you try that? Was it Package Explorer? Were both projects non-shared?

Comment 3 Lars Vogel

2019-09-24 13:49:47 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.