[
https://issues.apache.org/jira/browse/SCM-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960284#comment-17960284
]
ASF GitHub Bot commented on SCM-154:
------------------------------------
jira-importer commented on issue #370:
URL: https://github.com/apache/maven-scm/issues/370#issuecomment-2964590019
**[Mike
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)**
commented
cvs and svn are usually already installed on any open source developer's
machine. bzr is not. Thus it is bzr that really presents the first big hurdle
for compilation.
Perforce is available for free to open source projects but it is much
tougher about licensing so I would agree it is best left as is.
Nevertheless, any compilation prerequisite and why it is required should be
documented with links to the necessary software on the maven scm site.
> Bazaar tests should not assume bzr is installed
> -----------------------------------------------
>
> Key: SCM-154
> URL: https://issues.apache.org/jira/browse/SCM-154
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-bazaar
> Affects Versions: 1.0-beta-3
> Reporter: Mike Perham
> Assignee: Olivier Lamy
> Priority: Critical
> Fix For: 1.7
>
>
> Bazaar breaks my SCM build because it assumes it is installed. I do not
> think the user should be forced to install Bazaar just to compile the SCM
> codebase. See the StarTeam, Perforce and ClearCase providers for examples of
> providers which do not assume an installation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
