Support `baseuri` tagged values consistently in newly supported `.eapx`, `.qea`, `.qeax` and `.feap` schemas to match the historical use observed when using multiple `.xmi` files #156
A follow on task after the CIMTool 2.1.0 release is to extensively test and address known issues related to profiling custom extensions using the newly supported 64-bit EA 16.x .qea, .qeax, and '.feap' project file types introduced in 2.1.0. This was decided before 2.1.0 shipped in order to not hold up things up for end users that only needed to profile using normative CIM without extensions. Testing for 2.2.0 should also include 32-bit EA 15.x (and earlier) .eap and .eapx project files. The outcome of this effort is to allow for a single EA project file (e.g. .qea or .eap) to be used for modeling and profiling extensions which allows for the use of the baseuri tagged value to be used for specifying the namespaces for extensions modelling. The results should mirror what the same historical behavior as when using baseuri along with multiple .xmi files in a project with custom extensions.
A follow on task after the CIMTool 2.1.0 release is to extensively test and address known issues related to profiling custom extensions using the newly supported 64-bit EA 16.x
.qea,.qeax, and '.feap' project file types introduced in 2.1.0. This was decided before 2.1.0 shipped in order to not hold up things up for end users that only needed to profile using normative CIM without extensions. Testing for 2.2.0 should also include 32-bit EA 15.x (and earlier).eapand.eapxproject files. The outcome of this effort is to allow for a single EA project file (e.g..qeaor.eap) to be used for modeling and profiling extensions which allows for the use of thebaseuritagged value to be used for specifying the namespaces for extensions modelling. The results should mirror what the same historical behavior as when usingbaseurialong with multiple.xmifiles in a project with custom extensions.