Feature #8435
closedFeature #8434: Get rid of job classes
Always start up the same Core components
0%
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.
Updated by Evgeny Novikov about 7 years 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.
Updated by Evgeny Novikov over 6 years ago
- Target version changed from 2.0 to 1.0
Updated by Evgeny Novikov over 6 years ago
- Target version changed from 1.0 to 2.0
Updated by Ilja Zakharov about 6 years ago
- Status changed from New to Resolved
Implemented in klever-2.0.
Updated by Evgeny Novikov about 6 years 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.