jira-importer opened a new issue, #1211: URL: https://github.com/apache/maven-scm/issues/1211
**[Niels Basjes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nielsbasjes)** opened **[SCM-981](https://issues.apache.org/jira/browse/SCM-981?redirect=false)** and commented The README.md states > Run all the tests with `mvn -Prun-its verify` to assure nothing else was accidentally broken. The Github actions reuses for the CI build ```java apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml@v2 ``` which does the same ```java ./mvnw --errors --batch-mode --show-version -D"invoker.streamLogsOnFailures" -P run-its verify ``` https://github.com/apache/maven-gh-actions-shared/blob/v2/.github/workflows/maven-verify.yml#L167 https://github.com/apache/maven-gh-actions-shared/blob/v2/.github/workflows/maven-verify.yml#L93 The snag is that this profile does not exist in this project. I asked this and was told to use the `tck-git` profile https://github.com/apache/maven-scm/pull/134#issuecomment-1130214768 I found that there is also a `tck-svn` profile and a `tck` profile. When I run `mvn clean verify -Ptck` there are several tests that fail and are apparently never run by anyone. Proposal: * Create a profile run-its that simply activates the appropriate tck profiles. * Fix the failing tests. --- **Remote Links:** - [GitHub Pull Request #140 ](https://github.com/apache/maven-scm/pull/140) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
