[#SCM-154] Bazaar tests should not assume bzr is installed

Maven SCM

Bazaar tests should not assume bzr is installed

Created: 07/Feb/06 10:19 AM Updated: 25/Oct/06 05:23 PM

Component/s:

maven-scm-provider-bazaar

Affects Version/s:

1.0-beta-3

Fix Version/s:

future

Time Tracking:

Not Specified

Issue Links:

Related

This issue relates to:

~~SCM-230~~ mercurial plugin

Complexity:

Intermediate

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Emmanuel Venisse added a comment - 07/Feb/06 10:34 AM

I'm not really agree. We require installed cvs and svn for tests of cvs and svn providers because they are free, easy to install. With them we can run TCK tests. I consider it's the same for bazaar.
Clearcase, Perforce and Starteam aren't require by tests because they aren't available for free or easy to install.

[ Permlink | « Hide ]

Mike Perham added a comment - 07/Feb/06 10:45 AM

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.

[ Permlink | « Hide ]

Emmanuel Venisse added a comment - 07/Feb/06 10:52 AM

I added a note in bazaar provider directory

[ Permlink | « Hide ]

Ryan Daum added a comment - 25/Oct/06 05:23 PM

Whatever decision is made on this issue will also impact the in-development Mercurial provider, which was based on the Bazaar code base.