Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338055 - NatureManager.isNatureEnabled() gives invalid result when called after project import.
Summary: NatureManager.isNatureEnabled() gives invalid result when called after projec...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.7   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.7 M6   Edit
Assignee: Malgorzata Janczarska CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 273079 (view as bug list)
Depends on:
Blocks: 338074 338076 338077
  Show dependency tree
 
Reported: 2011-02-24 03:53 EST by Malgorzata Janczarska CLA
Modified: 2012-04-03 07:32 EDT (History)
1 user (show)

See Also:

Attachments
Fix (12.99 KB, patch)
2011-02-24 04:02 EST, Malgorzata Janczarska CLA 		Szymon.Brandys: iplog+
Details | Diff
Test updated (4.80 KB, patch)
2011-02-24 06:52 EST, Szymon Brandys CLA 		no flags Details | Diff
View All 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 Malgorzata Janczarska CLA 2011-02-24 03:53:46 EST 
NatureManager.isNatureEnabled() gives invalid result when called after project import. If NatureManager.isNatureEnabled() id called too early after project import it gives false result for new natures and the value is cached, so the invalid result is from not on returned until the project is reopened.
Comment 1 Malgorzata Janczarska CLA 2011-02-24 04:02:13 EST 
Created attachment 189676 [details]
Fix
Comment 2 Szymon Brandys CLA 2011-02-24 06:52:09 EST 
Created attachment 189687 [details]
Test updated

I changed the test a bit. The fix looks good.
Comment 3 Szymon Brandys CLA 2011-02-24 07:13:59 EST 
I released changes to HEAD. Thanks Gosia. Please open bugs for the older streams (3.4.2, 3.5.2 and 3.6.2) to backport the fix.
Comment 4 Malgorzata Janczarska CLA 2011-02-24 07:34:08 EST 
3.4.2+: Bug 338074
3.5.2+: Bug 338076
3.6.2: Bug 338077
Comment 5 Szymon Ptaszkiewicz CLA 2012-04-03 07:32:35 EDT 
*** Bug 273079 has been marked as a duplicate of this bug. ***