Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317663 - Better handling of naming conflicts when binding into workspace
Summary: Better handling of naming conflicts when binding into workspace
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-23 04:23 EDT by Thomas Hallgren CLA
Modified: 2019-02-25 14:41 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Hallgren CLA 2010-06-23 04:23:51 EDT 
Projects that have a project name that conflicts with the expected name (such as features not named with .feature or -feature at the end) does not bind correctly to the workspace when they conflict with other projects using the same name (a bundle for instance).
Comment 1 Thomas Hallgren CLA 2010-06-23 04:26:09 EDT 
Fixed this so that a warning is printed but the bind proceeds. The name in the .project is overridden by the name determined by Buckminster using rules and mspec patterns.

Fixed released to branch helios-maintenance, rev. 11481.