Changelog¶

Here are listed all the meaningfull changes done on nmk-base since version 1.0

Note

Only interface and important behavior changes are listed here.

The fully detailed changelog is also available on Github

Release 1.5.0¶

Add new build sub-tasks, to help other plugins hooking in the build phase at the right place:

Config items update:
- added ${requestFunction}: name of request function used for download tasks
- added ${javaRuntime} and ${javaRuntimeCustomPath}: used to resolve java command
API update:
- updated nmk_base.resolvers.FilesResolver to make it a “ready to use” resolver, with parameters
- moved nmk_base.resolvers.MultiChoiceResolver (and sub-classes) from nmk_base.common module, for more consistency
- added nmk_base.common.DownloadBuilder builder to handle download tasks (with progress bar + extraction option)
- added nmk_base.resolvers.CommandResolver resolver, to resolve a given command from a provided custom path or from system path

Config items changes:
- Update ${venvName}: make it dynamic WRT. current environment backend.
- Add ${venvRoot}: get the venv root folder.
- Add ${venvUpdateInput}: overridable input file for py.venv task.
- Add ${backendUseRequirements}: state if the environment backend uses a requirements file.
- Add ${backendLegacy}: state if the environment backend implementation is a legacy one.
- Add ${buildenvFolder}: legacy buildenv folder.
- Update ${buildenvRefresh}: disable buildenv loading scripts generation for buildenv version >= 2.
py.venv and py.req tasks inputs/outputs + behavior update to adapt to different environment backends.
API update: added nmk_base.common.MultiChoiceResolver (+ subclasses) resolvers for factorized config item multi-choice resolution.