Bug #2517
Fix/document variable resolution order
| Status: | Resolved | Start date: | 03/13/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Moringen | % Done: | 100% | |
| Category: | Processing Model | |||
| Target version: | 0.7 |
Description
Original report: https://opensource.cit-ec.de/issues/474
ich habe mal ein paar issues in Form eines Beispiels gesammelt:
Die letzten 3 commits in https://opensource.cit-ec.de/projects/citk/repository?utf8=%E2%9C%93&rev=buildgen-bugs sind:
- e4d9b9d test variable definition order 2 hours ago Robert Haschke
Test der Variablen-Definitions-Reihenfolge (sehr aufschlussreich!, sollte in die Doku)
- variable order:
no cmdline.variable define
distribution vars
template vars
project vars
project version vars
project version vars
template job varsIst es korrekt, das die "project version vars" zweimal konsultiert werden?
Associated revisions
Fixed duplicate inclusion of variables in src/project/classes-spec.lisp
fixes #2517
Do not include the `version-spec''s variables in each instantiated job
since the parent object, i.e. the newly made `version' already has them
and with the correct precedence, too.
- src/project/classes-spec.lisp (instantiate version-spec): do not
include the `version-spec''s variables in each instantiated job
History
#1 Updated by J. Moringen about 7 years ago
- Description updated (diff)
#2 Updated by J. Moringen about 7 years ago
Ist es korrekt, das die "project version vars" zweimal konsultiert werden?
Sounds like a bug, I will have a look.
#3 Updated by J. Moringen over 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset caca92ed7967db5c2016917dc80a1865ca7e83ca.
#4 Updated by J. Moringen over 6 years ago
- Target version set to 0.7