[LOGGING-185] mvn verify should also be run as part of the github actions workflow

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Assignee: Unassigned
• Reporter: Samael Bate
• Created: 31/Aug/23 22:50
• Updated: 19/Nov/23 18:38
• Resolved: 19/Nov/23 18:38

Description

mvn verify should be run as part of the build pipeline. 

The integration tests are currently broken and I believe they have been since this PR was merged because it introduced static imports to org.junit.Assert which is not on the classpath when running mvn verify.

There is also some incorrect config in the failsafe plugin.

By reverting the change to both ParentFirstTestCase.java and SecurityForbiddenTestCase.java in that PR and fixing the pom I was able to successfully run the tests.

 

 

Issue Links

• links to: GitHub Pull Request #157
• links to: GitHub Pull Request #180