Github user owenfarrell commented on the issue: https://github.com/apache/maven-surefire/pull/157 One workaround for this would be to install the missing `it-parent` POM as part of my first lifecycle (i.e. mid-test). But this seems kind of hacky. ``` <project> <artifactId>surefire-569-testjar</artifactId> ... <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-install-plugin</artifactId> <executions> <execution> <goals> <goal>install-file</goal> </goals> <phase>install</phase> <configuration> <file>${project.basedir}/../pom.xml</file> <pomFile>${project.basedir}/../pom.xml</pomFile> </configuration> </execution> </executions> </plugin> </plugins> </build> </project> ```
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org