You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The Java Plugin try to modify the project properties on-the-fly as the following example.
During executing integration test, the MavenExecutionResult only collect the properties statically defined in the testing pom.xml.
In this case it only prints project.build.sourceEncoding:UTF-8
@MavenJupiterExtensionclassHelloMojoIT {
@MavenTestvoidsimpleHello(finalMavenExecutionResultproject) {
MavenITAssertions.
assertThat(project).
isSuccessful();
/* * This only print the propertied defined at the testing pom.xml. * * The properties appended by the Java Plugin are not here. */project.getMavenProjectResult().
getModel().
getProperties().
entrySet().
forEach(
e -> System.out.println(e.getKey() + ":" + e.getValue())
);
}
}
Describe the solution you'd like
It would be great if the ITF is able to collect the project properties modified by the Java Plugin to the result.
Describe alternatives you've considered
At the moment, I use the gmavenplus-plugin to print out those modified by java plugin project properties and use the assertion to compare string from the stdout.
Is your feature request related to a problem? Please describe.
The Java Plugin try to modify the project properties on-the-fly as the following example.
During executing integration test, the
MavenExecutionResult
only collect the properties statically defined in the testingpom.xml
.In this case it only prints
project.build.sourceEncoding:UTF-8
Describe the solution you'd like
It would be great if the ITF is able to collect the project properties modified by the Java Plugin to the result.
Describe alternatives you've considered
At the moment, I use the gmavenplus-plugin to print out those modified by java plugin project properties and use the assertion to compare string from the
stdout
.Additional context
N/A
The text was updated successfully, but these errors were encountered: