This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 300885 - TigerstripeProjectAuditor indexing holding stale project references.
Summary: TigerstripeProjectAuditor indexing holding stale project references.
Status: RESOLVED FIXED
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-26 13:07 EST by Jim Strawn CLA
Modified: 2011-05-18 15:06 EDT (History)
1 user (show)

See Also:


Attachments
eclipse log. (14.46 KB, application/octet-stream)
2010-01-26 13:07 EST, Jim Strawn CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Strawn CLA 2010-01-26 13:07:04 EST
Created attachment 157313 [details]
eclipse log.

The issue can generally be replicated by the following:

1. Delete existing workspace and open eclipse (new workspace)
2. Create new Tigerstripe project (TestProjectOne)
3. Create new Tigerstripe project (TestProjectTwo)
4. Create a new package (at root level) in TestProjectOne named "root"
5. Create two new entities under "root" package in TestProjectOne
6. Refactor "root" to be renamed to "root1". Note that entities create
    created in 5 are now gone but no error messages are present in log.
7. Delete TestProjectOne and TestProjectTwo.
8. Create new Tigerstripe project (TestModelOne)
9. Create new Tigerstripe project (TestModelTwo)
10. Create a new package (at root level) in TestModelOne named "root"
11. Create two new entities under "root" package in TestModelOne (Named 
       as above)
12. Refactor "root" to be renamed to "root1". Note that entities create
       created in 11 are now gone.
13. See attached log file. This was generated by step 12.
Comment 1 Navid Mehregani CLA 2011-05-18 15:06:51 EDT
This has already been fixed with a bunch of refactoring fixes that were submitted between I32-I34.