Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1
    • Component/s: maven-scm-provider-git
    • Labels:
      None
    • Environment:
      Developed on Mac OS X 10.3.9 with git 1.2.4
    • Complexity:
      Intermediate
    • Testcase included:
      yes
    • Number of attachments :
      4

      Description

      Please find the git provider as attachment.

      Usefulness:
      I used the git provider together with [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin], it works fine for that use case.

      Open issues:

      • the JUnit tests are "proprietary", not yet TCK. I'll fix that.

      If you want to run the tests, you must have git installed and it must be in your PATH.

      To run git:

      • on Windows: use Cygwin and install the binutils, openssh, openssl, rsync, curl
        than you are able to compile and install git
      • on Linux: there are packages somewhere
      • on Mac OS X: use the DarwinPorts
      1. git.patch
        102 kB
        Dominik Winter
      2. git.tar.bz2
        15 kB
        Dominik Winter
      3. SCM-182.patch
        0.6 kB
        Dominik Winter
      4. update1.patch.bz2
        11 kB
        Heinrich Nirschl

        Activity

        Hide
        Don Brown added a comment -

        How, in any way, is this screwing with the community? First of all, having a separate version of the scm 1.1 provider prevents you from having to modify the release plugin in order to pull in the scm plugin, and second, the code works so why not have a tagged release today for those of us that don't want to wait for Maven 1.1?

        Open Source is about the freedom to be able to scratch your itch and share the solution with others; not about some ivory tower club dictating what the masses use. My branch is freely available in the Maven sandbox, so if you see something you'd like to merge back or even contribute, please feel free.

        Show
        Don Brown added a comment - How, in any way, is this screwing with the community? First of all, having a separate version of the scm 1.1 provider prevents you from having to modify the release plugin in order to pull in the scm plugin, and second, the code works so why not have a tagged release today for those of us that don't want to wait for Maven 1.1? Open Source is about the freedom to be able to scratch your itch and share the solution with others; not about some ivory tower club dictating what the masses use. My branch is freely available in the Maven sandbox, so if you see something you'd like to merge back or even contribute, please feel free.
        Hide
        Eugene Kuleshov added a comment -

        Don, please read my comment. You don't need to release, just lock the version. And again, if it works, why didn't you ask for release in the Maven dev list?

        Show
        Eugene Kuleshov added a comment - Don, please read my comment. You don't need to release, just lock the version. And again, if it works, why didn't you ask for release in the Maven dev list?
        Hide
        Mark Struberg added a comment -

        Eugene, are you and Jason cleaning the snapshot repo at sonatype on a regular basis, or will the snapshot remain there 'forever'?
        (I ask this, because in our company I do clean our snapshot repo every month to ensure that nobody is using snapshot versions in production).

        There are many roads leading to Rome, and I have to admit that the most important part in this discussion (at least for me as author) is to hear that the plugin is useful for the community and it now works out of the box for many people. So, I'm not screwed but rather happy to hear that Don succeed using it. Plus: the more attraction it gets, the more people will try using git with maven since there is no showstopper in this scenario anymore!

        I will ask for the status and plans for scm-1.1 in the scm dev list.

        Show
        Mark Struberg added a comment - Eugene, are you and Jason cleaning the snapshot repo at sonatype on a regular basis, or will the snapshot remain there 'forever'? (I ask this, because in our company I do clean our snapshot repo every month to ensure that nobody is using snapshot versions in production). There are many roads leading to Rome, and I have to admit that the most important part in this discussion (at least for me as author) is to hear that the plugin is useful for the community and it now works out of the box for many people. So, I'm not screwed but rather happy to hear that Don succeed using it. Plus: the more attraction it gets, the more people will try using git with maven since there is no showstopper in this scenario anymore! I will ask for the status and plans for scm-1.1 in the scm dev list.
        Hide
        Olivier Lamy added a comment -

        As the branch in the sandbox looks to works.
        We can merge it to trunk.
        Objections ?

        Show
        Olivier Lamy added a comment - As the branch in the sandbox looks to works. We can merge it to trunk. Objections ?
        Hide
        Olivier Lamy added a comment -

        ok no merge needed.

        Show
        Olivier Lamy added a comment - ok no merge needed.

          People

          • Assignee:
            Olivier Lamy
            Reporter:
            Dominik Winter
          • Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: