Currently the pitest JARs are part of the Git repository and I guess updating to a new version of pitest requires manually downloading JARs and updating the MANIFEST
Proposed Solution
By using maven-dependency-plugin we can specify pitest dependencies in the POM and then have the Maven plugin create a libs folder inside the project (which would be excluded from Git); JARs can also be copied without their version, so that updating to a new version of pitest is just a matter of changing the version in the POM.
Motivation
Currently the pitest JARs are part of the Git repository and I guess updating to a new version of pitest requires manually downloading JARs and updating the MANIFEST
Proposed Solution
By using
maven-dependency-pluginwe can specify pitest dependencies in the POM and then have the Maven plugin create alibsfolder inside the project (which would be excluded from Git); JARs can also be copied without their version, so that updating to a new version of pitest is just a matter of changing the version in the POM.I'll provide a PR ASAP