v0.5.0

What's Changed

• Fail ignition build when the same jar in moduleContent folder with multiple versions detected by @ia-vzhang in #68

New Contributors

• @ia-vzhang made their first contribution in #68

Full Changelog: v0.4.1...v0.5.0

v0.4.1

What's Changed

• Add DuplicatesStrategy to sync task in CollectModlDependencies by @jjcoffman in #64

Full Changelog: v0.4.0...v0.4.1

v0.4.0

New --foldJars option for writeModuleXml task

All project versions in this monorepo are synced for simplicity now; the generator core and CLI, and the plugin are all at 0.4.0.

What's Changed

• Support lazy evaluation of signed module output file by @benmusson in #55
• De-duplicate Module.xml jar entries based on scope. by @benmusson in #53
• Clean up filename and required ignition version templates by @paul-griffith and @brianeray in #58
• Gradle error on fresh generated module skeleton by @brianeray in #59

New Contributors

• @benmusson made their first contribution in #55

Full Changelog: v0.3.0...v0.4.0

v0.3.0

New required flag for module dependencies

What's Changed

• Add ability to support "required" flag in module dependencies of module.xml by @ia-keaton in #48

New Contributors

• @ia-keaton made their first contribution in #48

Full Changelog: v0.2.0...v0.3.0

v0.2.0

PKCS#11 signing

Allows for signing modules via PKCS#11 keystores like hardware tokens and cloud keystores. Also fixes an UP-TO-DATE check with :collectModuleDependencies.

What's Changed

• add support for kts-based buildscripts by @PerryAJ in #32
• Fix sample kts in README for ignition gradle module plugin by @maroc81 in #34
• fix common scope project dependencies by @PerryAJ in #35
• IGN-6325: collectModlDependencies detects source changes by @brianeray in #39
• IGN-7871 PKCS#11 signing by @brianeray in #43

New Contributors

• @maroc81 made their first contribution in #34
• @brianeray made their first contribution in #39

Full Changelog: v0.1.1...v0.2.0

v0.1.1

Add skipModlSigning option

An additional boolean property skipModlSigning has been added to ModuleSettings extension to allow for the creation of unsigned modules. The task ordering has not been modified, but the emitted modl file and buildResult.json now reference the *.unsigned.modl file instead along with additional logging for the SignModule task alerting the user that module signing will be skipped.

This is useful for early development of a module for a development gateway which has support for unsigned modules enabled. This mode should not be used for production as it is a potential security risk.