[incubator-kie-issues#1834] DMN: verify namespaces are always aligned

[gitgabrio]

Fixes apache/incubator-kie-issues#1834

Needs: apache/incubator-kie-kogito-runtimes#3849

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

• for pull request and downstream checks

  • Push a new commit to the PR. An empty commit would be enough.

• for a full downstream build

  • for github actions job: add the label run_fdb

• for Jenkins PR check only

  • If you are an ASF committer for KIE podling, login to Jenkins (https://ci-builds.apache.org/job/KIE/job/drools/), go to the specific PR job, and click on Build Now button.

[jomarko]

It seems some dmn models start to fail validation in kogito-runtimes now?

[jomarko]

Thank you for a PR @gitgabrio

[jomarko]

Hmm, this code change open a question in me, what should our tooling to do if an inconsistent namespaces are present in opened file.

[baldimir]

Maybe we should ask the user a question if they want to update it and if they confirm, then Canvas could fix it for them.

[gitgabrio]

DMN version is an atomic entity that comprise also FEEL, DMNDI, DI, and DC.
Even if they are defined under different namespaces for technical reason, as a matter of fact they are all part of the same version.
So, switching DMN version should imply that all of them are kept in sync with that version, otherwise the model will be in inconsistent state.

[gitgabrio]

@baldimir @yesamer
Please be aware of the management of FEEL namespace.
With newer version (1.6) and the B-FEEL, it seems that there won't be anymore a 1:1 relationship between DMN and FEEL namespace. That will need to be addressed in following PRs