Project

General

Profile

Actions

Bug #11010

closed

Take into account aspects when caching models

Added by Evgeny Novikov about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Urgent
Category:
Tasks generation
Target version:
Start date:
11/11/2021
Due date:
% Done:

0%

Estimated time:
Detected in build:
git
Platform:
Published in build:

Description

If one runs verification of several requirement specifications within one job and simultaneously requires to use aspects of those requirement specifications for weaving common models, current caching approach can fail since it will cache and then reuse models that are woven in using only one aspect(s) from one requirement specification while other ones can require other aspects being used. I suppose to distinguish not only models but also aspects when caching them.


Related issues 1 (0 open1 closed)

Related to Klever - Bug #10476: Distinguish models by their absolute paths rather than their contentsClosedEvgeny Novikov08/27/2020

Actions
Actions #1

Updated by Evgeny Novikov about 1 year ago

  • Related to Bug #10476: Distinguish models by their absolute paths rather than their contents added
Actions #2

Updated by Evgeny Novikov about 1 year ago

  • Status changed from New to Closed

I resolved this in branch bug-11010. After that branch passed tests, I merged it to master in b63d006ca.

Actions

Also available in: Atom PDF