Maven SCM

Bazaar tests should not assume bzr is installed

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 1.0-beta-3
  • Fix Version/s: future
  • Component/s: maven-scm-provider-bazaar
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

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.

Issue Links

This issue relates to:
SCM-230 mercurial plugin Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Venisse added a comment -

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.

Show
Emmanuel Venisse added a comment - 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.
Hide
Permalink
Mike Perham added a comment -

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.

Show
Mike Perham added a comment - 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.
Hide
Permalink
Emmanuel Venisse added a comment -

I added a note in bazaar provider directory

Show
Emmanuel Venisse added a comment - I added a note in bazaar provider directory
Hide
Permalink
Ryan Daum added a comment -

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

Show
Ryan Daum added a comment - Whatever decision is made on this issue will also impact the in-development Mercurial provider, which was based on the Bazaar code base.
Hide
Permalink
Mark Struberg added a comment - - edited

This is pretty easy to solve. Simple move all unit tests into some *TckTest.java classes. So they will only run if you specify -Ptck

Show
Mark Struberg added a comment - - edited This is pretty easy to solve. Simple move all unit tests into some *TckTest.java classes. So they will only run if you specify -Ptck

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.