[ http://jira.codehaus.org/browse/SCM-139?page=all ]
Dennis Lundberg closed SCM-139. ------------------------------- Resolution: Fixed After adding a couple of more tests, I committed the new utility class. I also searched for similar code in other classes and replaced it with calls to methods in the new utility class. > Create a utility class for scm url checking/parsing > --------------------------------------------------- > > Key: SCM-139 > URL: http://jira.codehaus.org/browse/SCM-139 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api > Reporter: Dennis Lundberg > Assigned To: Dennis Lundberg > Fix For: 1.0 > > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira