-
Notifications
You must be signed in to change notification settings - Fork 41.5k
Document how to configure Maven's Failsafe plugin when not using spring-boot-starter-parent #25621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ven failsafe plugin when not using parent pom
Change NOTE to WARNING
Thanks for the pull request, @robert-smith-911. Unfortunately, this isn't quite what I had in mind. Rather than changing the configuration of <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
<configuration>
<classesDirectory>${project.build.outputDirectory}</classesDirectory>
</configuration>
</plugin> AFAIK, using this approach also means that there's no custom configuration required when the module path's in the picture. Would you like to update your proposal along these lines? |
Aha sure @wilkinsona no problem! |
@robert-smith-911 how is it going? Would you have time to update this PR? |
@snicoll Yes sir just got busy at work, doing it today thanks for the reminder |
@snicoll @wilkinsona How's this? |
Thanks very much, @robert-smith-911. If you're interested a polished the proposed changes a little bit, primarily to move the updates into the integration testing section of the documentation. |
@wilkinsona sure! |
A documentation fix for #25473 to document how to configure maven's failsafe plugin when not using spring boot starter parent pom.