This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 244018 - After switching off TigerstripeProjectAuditor still get audits running
Summary: After switching off TigerstripeProjectAuditor still get audits running
Status: CLOSED WORKSFORME
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: 0.4   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 0.4M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-13 08:16 EDT by John Worrell CLA
Modified: 2012-03-05 14:12 EST (History)
2 users (show)

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 John Worrell CLA 2008-08-13 08:16:20 EDT 
When constructing a model using the API with TigerstripeProjectAuditor switched off using TigerstripeProjectAuditor.setTurnedOffForImport(true) I find that ausits are still running  with unfortunate consequences. One consequence seems to be that it can encounter incompletely constructed associations, and another seems to be that I get ConcurrentModificationExceptions when the auditor includes checks against annotations and annotations are being added by the importer.

What seems to be happening is that whereas the regular audits are swichted off, the pending audits still go through ie. are not protected by the check against the isTurnedOffForImport flag. I suggest we defer running the pending auits until after the audit falg is re-set to false.
Comment 1 Richard Craddock CLA 2008-10-24 04:54:07 EDT 
I am seeing the project building during a UML import.

This is pretty annoying and slows it down considerably!
Comment 2 Richard Craddock CLA 2009-02-02 06:41:41 EST 
Upping severity as this significantly slows down any import....
Comment 3 Navid Mehregani CLA 2012-03-05 14:12:59 EST 
I'm unable to reproduce this issue.  Please reopen if you can still reproduce it.