[
https://issues.apache.org/jira/browse/SCM-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963966#comment-17963966
]
ASF GitHub Bot commented on SCM-1009:
-------------------------------------
jira-importer opened a new issue, #1233:
URL: https://github.com/apache/maven-scm/issues/1233
**[Tamas
Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)**
opened
**[SCM-1009](https://issues.apache.org/jira/browse/SCM-1009?redirect=false)**
and commented
The maven-compat is enlisted as provided dependency of plugin, while it is
actually NOT needed at runtime (but due this warns in Maven 3.9.2+). The
maven-compat IS needed, but only in test scope.
---
**Remote Links:**
- [GH PR#170
](https://github.com/apache/maven-scm/pull/170)
> Wrong scope of maven-compat
> ---------------------------
>
> Key: SCM-1009
> URL: https://issues.apache.org/jira/browse/SCM-1009
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-plugin
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.1
>
>
> The maven-compat is enlisted as provided dependency of plugin, while it is
> actually NOT needed at runtime (but due this warns in Maven 3.9.2+). The
> maven-compat IS needed, but only in test scope.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
