Is this explicit override of library versions intended?

[gallardo]

Reviewing the code I came through this section of a pom:

serenity-core/serenity-smoketests/pom.xml

Lines 60 to 75 in 1bec1b7

	<dependency>
	<groupId>org.slf4j</groupId>
	<artifactId>slf4j-simple</artifactId>
	<version>1.7.30</version>
	</dependency>
	<dependency>
	<groupId>junit</groupId>
	<artifactId>junit</artifactId>
	<version>4.13.1</version>
	<scope>test</scope>
	</dependency>
	<dependency>
	<groupId>org.assertj</groupId>
	<artifactId>assertj-core</artifactId>
	<version>3.18.0</version>
	</dependency>

that overrides the versions of the libraries defined globally for serenity-bdd. Is there a reason for this? It looks wrong, and in fact, the versions are not the same... Should the versioning not be delegated to the dependencyManagement of the parent pom?

[wakaleo]

The smoketests module is separate from the main project, so does not necessarily use the same dependencies.