Closed monperrus closed 5 years ago
Hi thank for reporting this.
dspot-maven-plugin
has also another issue with TAF.
see below:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.github.claremontqualitymanagement.TestAutomationFramework:Core:jar:2.8.7
[WARNING] 'version' contains an expression but should be a constant. @ com.github.claremontqualitymanagement.TestAutomationFramework:Core:${capability.core.version}, /tmp/TestAutomationFramework/Core/pom.xml, line 13, column 14
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] --< com.github.claremontqualitymanagement.TestAutomationFramework:Core >--
[INFO] Building TAF - Core 2.8.7
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- dspot-maven:2.0.0:amplify-unit-tests (default-cli) @ Core ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.832 s
[INFO] Finished at: 2019-04-08T11:33:20+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal eu.stamp-project:dspot-maven:2.0.0:amplify-unit-tests (default-cli) on project Core: Unable to parse configuration of mojo eu.stamp-project:dspot-maven:2.0.0:amplify-unit-tests for parameter project: Cannot find default setter in class org.apache.maven.project.MavenProject -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginConfigurationException
Investigating both.
DSpot was failing on metamutator because of the class in the default package.
When no filter is specified, DSpot computes a filter on the fly and this filter was not correct.
I'm gonna open a new issue for TAF, because it is not the same issue.
trying to run
mvn eu.stamp-project:dspot-maven:amplify-unit-tests
on https://github.com/SpoonLabs/metamutator/it fails with