Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346784 - TS blocks creating a package if a similar artefact name exists in the same directory
Summary: TS blocks creating a package if a similar artefact name exists in the same di...
Status: RESOLVED WONTFIX
Alias: None
Product: Tigerstripe
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-21 09:24 EDT by Chris Hartley CLA
Modified: 2011-10-03 16:33 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Hartley CLA 2011-05-21 09:24:13 EDT
Create a new project

add package 'test'

under 'test' add an Entity called 'Test' - all works OK.

now under 'test' add an Entity called 'Cabbage'
now under 'test' add a sub-package called 'cabbage'

TS blocks this saying " Type with same name but different case exists."

So cancel out.
Go to the Java perspective
under 'test' add a sub-package called 'cabbage'
it works !!

So this will cause a lot of issues if this is not fixed !!!
Comment 1 Navid Mehregani CLA 2011-05-24 00:12:23 EDT
This has been scheduled for i35.
Comment 2 Navid Mehregani CLA 2011-06-03 11:42:39 EDT
The reason why TS blocks this scenario is because packages are treated just like any other Tigerstripe artifact.  

We'll need to make a design change in order to resolve this issue, which will imply change to refactoring logic, diagrams, UI, etc...  This defect has been moved out of i35 so it can be further discussed before any changes are made.
Comment 3 Navid Mehregani CLA 2011-10-03 16:33:31 EDT
I've decided to mark this defect as won't fix due to the risks involved in making the necessary design changes in Tigerstripe.  As stated in my previous comment, packages are treated as regular Tigerstripe artifacts, which is why the tooling prevents an entity artifact to be created under a package of the same name.  

If this defect is completely blocking you, please re-open it so it can be further discussed.