[GitHub] [maven-verifier] slawekjaranowski commented on pull request #9: [MSHARED-1043] Deprecate methods leveraging JUnit4 assertions

2022-03-12 Thread GitBox
slawekjaranowski commented on pull request #9: URL: https://github.com/apache/maven-verifier/pull/9#issuecomment-1065897499 @kwin - what with open conversations with @elharo -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

[GitHub] [maven-verifier] slawekjaranowski commented on pull request #9: [MSHARED-1043] Deprecate methods leveraging JUnit4 assertions

2022-03-11 Thread GitBox
slawekjaranowski commented on pull request #9: URL: https://github.com/apache/maven-verifier/pull/9#issuecomment-1065120081 Better stats is usage per version, like: https://mvnrepository.com/artifact/org.apache.maven.shared/maven-verifier -- This is an automated message from the Ap

[GitHub] [maven-verifier] slawekjaranowski commented on pull request #9: [MSHARED-1043] Deprecate methods leveraging JUnit4 assertions

2022-03-11 Thread GitBox
slawekjaranowski commented on pull request #9: URL: https://github.com/apache/maven-verifier/pull/9#issuecomment-1065118967 We shouldn't stop development based on simple usage. Eg. now many project migrate to JUnit 5 or use other test frameworks than JUnit 4. We shouldn't implica

[GitHub] [maven-verifier] slawekjaranowski commented on pull request #9: [MSHARED-1043] Deprecate methods leveraging JUnit4 assertions

2022-03-10 Thread GitBox
slawekjaranowski commented on pull request #9: URL: https://github.com/apache/maven-verifier/pull/9#issuecomment-1064592627 It is standard way, first deprecated method with documentation how should be replace - and we do this step. Next we release major version with removed methods i