Project

General

Profile

Feature #8435

Feature #8434: Get rid of job classes

Always start up the same Core components

Added by Evgeny Novikov over 1 year ago. Updated 5 months ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Infrastructure of Core
Target version:
Start date:
09/18/2017
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

A long ago I assumed that we will have a lot of job classes for various types of target programs, and for each such class it will be necessary to specify a corresponding component chain. Now I think that it would be better to always start up the same Core components while specify target program types in a job configuration. Core components will find appropriate plugins. That was already done for generation of verification and verification tasks. So, now this should be implemented for high-level components as well.

History

#1 Updated by Evgeny Novikov over 1 year ago

  • Assignee changed from Evgeny Novikov to Ilja Zakharov

Recently Ilja considerably improved/refactored Core itself, so, he is familiar very well with the problem.

#2 Updated by Evgeny Novikov 10 months ago

  • Target version changed from 2.0 to 1.0

#3 Updated by Evgeny Novikov 10 months ago

  • Target version changed from 1.0 to 2.0

#4 Updated by Ilja Zakharov 7 months ago

  • Status changed from New to Resolved

Implemented in klever-2.0.

#5 Updated by Evgeny Novikov 5 months ago

  • Status changed from Resolved to Closed

Branch klever-2.0 passed all tests and I merged it to master in 72be796e3 marked as v2.0rc1.

Also available in: Atom PDF