The reason for not including utilities of modelVersion < 10.0 is not clear

[edwingamboa]

AS-IS

When developing an artifact in [email protected] that has a utility with modelVersion < 10.x as a dependency, the component cannot be initialised and console errors are logged (See attached image).

The warning message about the modelVersion is as follows:

Webpackage with id [webpackageId] has modelVersion 9.1.1. This CRC (version=3.0.0-SNAPSHOT) supports the following modelVersion(s): 10.0

Then, the error message looks as follows:

The artifact '[artifact-id]' is not defined in manifest:
Dependency reference: ...

Although the DepMgr logs a warning indicating that the utility is not modelVersion 10.0 before those errors, it is not straightforward to conclude that the errors are due to the modelVersion.

TO-BE

The warning message should indicate that the webpackage will be not included as dependency, and not only say the utility has a different modelVersion.

Webpackage with id [webpackageId] has modelVersion 9.1.1, and this CRC (version=3.0.0-SNAPSHOT) supports the following modelVersion(s): 10.0. Thus, the webpackage and its artifacts will be excluded.

[edwingamboa]

@jtrs @pwrinc I just noticed that the warnings about the modelVersion are logged. However, I think that is not straightforward to relate the errors to the warnings. The error message says that the artifact is not defined in the manifest, however, it is actually defined but was excluded due to the modelVersion.

[pwrinc]

Suggestion: Throw an error instead of the warning. If this error occurs we should stop Dependency Resolution (suppress event DepMgr ready and throw a new error Event).