Fix for missing classes required on executeStopOnVMShutdown:true

[Smiche]

I encountered the following issue:

Using:

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: C:\Program Files\apache-maven
Java version: 17.0.12, vendor: Eclipse Adoptium, runtime: C:\Program Files\Java\jdk-17.0.12+7
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Adding the two required classes to the Class loader resolved the issue. I didn't go in too deep why that check using Strings occurs.

Here's the execution config which lead to this:

					<execution>
						<id>remove-it-database</id>
						<goals>
							<goal>stop</goal>
						</goals>
						<configuration>
							<executeStopOnVMShutdown>true</executeStopOnVMShutdown>
							<removeVolumes>true</removeVolumes>
							<skip>${skipTests}</skip>
						</configuration>
						<phase>pre-integration-test</phase>
					</execution>

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[rhuss]

Thanks for spotting this! An alternative solution would be to remove Guava altogether from the code base, it doesn't add many benefits (except causing issues like these :)

@rohanKanojia wdyt ? On the other hand, this is a quick fix without any side-effects asfais, so would be happy to merge it, too.

[Smiche]

Sounds like a better fix indeed. It was barely used for things that don't even need it. Great plugin by the way.