Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Uncouple bridge generation from mappings refresh.
We change the "refresh-external-resources" target so that it still refreshes (1) the imports, (2) the "local" imports (in fact the local copies of the foreign ontologies used to build Composite Metazoan), (3) the externally maintained mapping sets, (4) the externally maintained bridges; BUT it does not re-generate the bridge files that are dependent on the refreshed mappings. The mappings-derived bridges are now expected to be built at release time (and also at QC time). We build them under MIR=false, so they will only be built using the locally available mappings (from the last time they were refreshed), without triggering the download of any remote resource. Editors/maintainers can still locally trigger the building of the bridge files at any time by explicitly invoking the "refresh-bridges" target, if they want/need to do so. This does not change anything for whoever is running the refresh pipeline nowadays: it's still only a matter of invoking "refresh-external-resources". The only difference is that this won't trigger a rebuild of the bridge files. Two benefits: the "refresh imports" PRs will no longer be polluted by needless changes in the bridge files, in which only the version IRI has changed; the bridge files will always be generated (at least) at the same time as the release, so they will always have a correct version IRI. Minor cosmetic changes also in this commit: * "CUSTOM_BRIDGES" is renamed to "EXTERN_BRIDGES", which reflects better the true nature of those bridges (it does not really matter that they are "custom", what matters is that they are not generated here). * We use MIR=false, rather than IMP=false, to prevent the downloading of any remote resource. This is for consistency with other parts of the Makefile. closes #3438
- Loading branch information