Github user bindul commented on the issue: https://github.com/apache/maven-surefire/pull/173 @Tibor17 I have reviewed the Maven Coordinates documentation you mentioned, and I can switch the order of elements in the parameter easily. However, I think I would disagree with requiring the version to be last element in the coordinates in this use case. As the functionality stands, the `dependenciesToScan` configuration does not add additional dependencies to the test scope of the project, it filters dependencies already added to the test scope in the project to allow for scanning test classes to run. If someone wants to add say a classfier or a type/packaging, requiring them them to also mention the version of the dependency would just make maintainers life harder by having another location to keep the version of the dependency in sync. As such I propose, we keep the version as optional and support the following variations of dependencies to scan: - `groupId:artifactId` - `groupId:artifactId:packaging/type` - `groupId:artifactId:packaging/type::version` - `groupId:artifactId:packaging/type:classifier` - `groupId:artifactId::classifier` - `groupId:artifactId::classifier:version` - `groupId:artifactId:packaging/type:classifier:version` It still maintains the same order of elements as the Maven Coordinates documentation in the POM, just makes the version not required to be the last element, or rather makes version optional. Thoughts?