When doing changes to the kmodule.xml file (for example adding a default kbase, ksession and some work item handlers) through the Project Editor, or also when manually changing the module.xml, and then doing a Build & Deploy, the generated jar on the local maven repo doesn't always seem to contain the last version of the kmodule.xml file.  While the changes definitely seem to be recorded in the VFS (reopening in Project Editor or manually opening kmodule.xml seems to confirm this), the jar that is built doesn't always seem to be up-to-date.

It does seem to pick up changes sometimes, but it is unclear when / why.

To reproduce, create a project, in Project Editor create default kbase + ksession with work item handler.  Keep change the name of the work item handler, save and build & deploy, then check the generated jar for the contents of the kmodule.xml in there.  In my case, it didn't always include the latest version.

Note that this was reproduced on ER5 (with a cleared cache), it doesn't seem to occur (or less, or just plain luck?) on community build.