Pankraz76 commented on PR #2307: URL: https://github.com/apache/maven/pull/2307#issuecomment-2876015707
might use what we already got making things tight, instead of going crazy. When done only once right, we dont need rival. Going with most common default seems justiciable thus aligning with: > JUnit has a lot more than assertTrue. There's assertEquals, assertNull, assertSame, etc. I'm OK with things JUnit doesn't have like assertContains, but I don't want to replace things JUnit already has. Guava's MoreAsserts makes a lot more sense than AssertJ. It fills the potholes, not replaces the road. - https://github.com/apache/maven/pull/2330 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
