Setting version.ai.timefold.solver to 999-SNAPSHOT while the parent version remains on a different version may lead to inconsistencies in the dependency graph.
<parent>
<groupId>ai.timefold.solver</groupId>
<artifactId>timefold-solver-service-parent</artifactId>
<!--
Parent version must be the first <version> in the pom file due to release workflow.
Do not use version property for parent version as it's not supported by Dependabot.
-->
<version>2.4.0-rc-1</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>ai.timefold.model</groupId>
<artifactId>timefold-field-service-routing</artifactId>
<version>${revision}</version>
<name>Timefold Field Service Routing model</name>
<!-- Please see .mvn/maven.config for Timefold Model SDK profiles activated by default. -->
<properties>
<revision>999-SNAPSHOT</revision>
<model.api.version>v1</model.api.version>
<version.org.locationtech.jts>1.20.0</version.org.locationtech.jts>
<version.org.jgrapht>1.5.3</version.org.jgrapht>
<!-- if needed, override defaults from timefold-models-sdk-model-parent -->
<maven.compiler.release>25</maven.compiler.release>
<!-- to avoid warning in tests due to Mockito's ByteBuddy -->
<argLine>-XX:+EnableDynamicAgentLoading</argLine>
<version.ai.timefold.solver>999-SNAPSHOT</version.ai.timefold.solver>
</properties>
Setting
version.ai.timefold.solverto999-SNAPSHOTwhile the parent version remains on a different version may lead to inconsistencies in the dependency graph.