[
https://issues.apache.org/jira/browse/SCM-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960167#comment-17960167
]
ASF GitHub Bot commented on SCM-139:
------------------------------------
jira-importer commented on issue #343:
URL: https://github.com/apache/maven-scm/issues/343#issuecomment-2964586727
**[Dennis
Lundberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=denn...@apache.org)**
commented
Attaching a draft of what the API might look like. The implementation is not
done yet, this is just a requst for comments. Please have a look at it and tell
me what you like/dislike and if there are other useful methods that can be put
in there.
> Create a utility class for scm url checking/parsing
> ---------------------------------------------------
>
> Key: SCM-139
> URL: https://issues.apache.org/jira/browse/SCM-139
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-api
> Reporter: Dennis Lundberg
> Assignee: Dennis Lundberg
> Priority: Major
> Fix For: 1.0-beta-4
>
> Attachments: SCM-139-2.zip, SCM-139.zip, ScmUrlUtils.java
>
>
> There is a lot of code in different places, both in maven-scm and elsewhere,
> that checks and parses scm url:s. I propose that a utility class ScmUrlUtils
> be crated in maven-scm-api where such code (static methods) can be placed.
> The code there should not be scm provider specific. This should be
> accompanied by a test suite.
> This concept might also be applied to individual scm providers, e.g. there
> could be a CvsScmUrlUtils in maven-scm-provider-cvs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
