Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Auto Closed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Unit tests succed on linux and windows.

      Description

      maven-scm provider implementation for monotone (http://www.venge.net/monotone/)

      The provider currently implements: add, checkin, checkout, status and tag

      Unit tests run on linux and windows; tested with release plugin on linux.

      One problem with the unit tests remains:
      I needed to manually create the 'scm-test' directory for the unit tests. Is this a bug in the test framework or should the provider create all missing directores as needed?

      1. SCM-276-provider.patch
        97 kB
        Tim Kettler
      2. SCM-276-provider.patch
        102 kB
        Tim Kettler
      3. SCM-276-site.patch
        5 kB
        Tim Kettler

        Activity

        Hide
        Emmanuel Venisse added a comment -

        If you look at actual providers like cvs provider you'll see the initrepo method use a pre-packaged repository stored in src/test/tck-repository/.
        If with your provider, you can't provide a pre-packaged repository, you need to create this directory in your tests or provide a patch for the TCK that create it.

        Show
        Emmanuel Venisse added a comment - If you look at actual providers like cvs provider you'll see the initrepo method use a pre-packaged repository stored in src/test/tck-repository/. If with your provider, you can't provide a pre-packaged repository, you need to create this directory in your tests or provide a patch for the TCK that create it.
        Hide
        Tim Kettler added a comment -

        Fixed the directory creation issue.

        Show
        Tim Kettler added a comment - Fixed the directory creation issue.
        Hide
        Michael Osipov added a comment -

        This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

        Show
        Michael Osipov added a comment - This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

          People

          • Assignee:
            Unassigned
            Reporter:
            Tim Kettler
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development