Closed smithdtyler closed 6 years ago
This is as expected. OSATE installs a resource listener to check if an AADL project was renamed. This kicks in for all changes to resources in the workspace.
I'm seeing 10+ concurrent "Rename AADL Project" tasks simultaneously.
Does this cause any problem?
It's hard to tell whether CPU is being eaten up, at a minimum it's confusing and hides the actual job being run.
On Tue, Dec 4, 2018 at 10:14 AM Lutz Wrage notifications@github.com wrote:
Does this cause any problem?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/osate/osate2/issues/1319#issuecomment-444157979, or mute the thread https://github.com/notifications/unsubscribe-auth/AHw_XEZs2NKErsA5pR6W0yWSZLJzacAvks5u1p9KgaJpZM4UoA0c .
Summary
When I save a non-AADL file, I see one or more tasks called "Rename AADL Project" in my Eclipse task status window.
Expected and Current Behavior
I don't have any AADL projects in my workspace, so I should not see this task running.
Steps to Reproduce
Environment
Eclipse Oxygen 3a OSATE 2.3.4.v20180531 Windows 7