Updated prime-core version to support tags in expansionResource.xml. Note that in previous versions, the
expansionResource goal will not recognize the tags and will drop them.
[VEGA-365] Fixed expansionResource goal throwing "Version string 'x' is not valid SemVer" if one of the dependencies
has more than 3 version numbers, in combination with the includeClassPathDependencies option.
[VEGA-354] Added parameter expansion.model.force, which forces expansion or harvest, even if there are model issues, such as
expired options. This feature is provided to support expansion of an earlier project version, it should not be used in
day-to-day use.
Plugin tasks now use the classpath as defined in the expansionSettings. Previously, the plugin would look at the
versions of prime-core and metamodel-runtime it was built against and insert them if they were newer.
The new behaviour instead tries to always use the versions extracted from the expansionSettings file.
The old behaviour is still available with the parameter -Dexpansion.versions.preserve=false.
Upgraded to prime-core 2023.9.1 to revert change which broke expanders older than 5.36.0 because of a missing
database schema/table option. The logic was moved to expanders, but this meant the new prime-core version
didn't work with older expander versions.
Added parameter validation.failIfError to validate-model. If it is true, the goal fails if a rule with priority
error fails. By default, it is set to true.
Goals documentation was no longer being generates because that functionality was moved from maven-plugin-plugin
to a separate maven-plugin-report-plugin plugin. (
See MPLUGIN-467)