zAppBuild 3.3.0
New & Noteworthy
This release delivers a new strategy for files that don't need to be scanned but are processed by language scripts - such as JCLs, XML files or other configuration files. Starting with this release, zAppBuild is only scanning a file for its dependencies when the file extension is specified it in the dbb.scannerMapping
property. The property mapping, being located in build-conf/defaultzAppBuildConf.properties, is carrying the default mappings. Important: If you have a requirement to scan files with different file extensions, please add them to the configuration. Independently of the scanner mapping, files will continue to be recorded as logical files in the collections.
The test framework was significantly updated and is now easier to use and also to extend with your own test bucket.
What's Changed
- Strategy to record logical files but skip scanning them by @dennis-behm in #30
- Tolerate old dbb.scannerMapping configurations by @dennis-behm in #385
- Avoid additional scan of build file during impact analysis by @dennis-behm in #371
- Refactoring Test Framework by @dennis-behm in #363
- Ability to maintain consistent information in the DBB metadata store for dependencies on generated zunit test case by @dennis-behm in #368
- Fix condition evaluating generated test cases and zunit processing by @dennis-behm in #382
- Fix sorting of build list when creating test case dependency programatically by @dennis-behm in #364
- Skip inspecting load modules when running in preview mode by @dennis-behm in #387
- Release zAppBuild 3.3.0 by @dennis-behm in #360
Full Changelog: 3.2.0...3.3.0