Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Out of scope
    • Affects Version/s: 0.11.0
    • Fix Version/s: None
    • Component/s: SCM
    • Labels:
      None
    • Global Rank:
      13457

      Description

      I installed Eclipse Java EE IDE for Web Developers. Version: Helios Service Release 1 Build id: 20100917-0705
      I installed M2Eclipse org.maven.ide.eclipse.feature 0.12.0.20101115-1102
      I installed M2Eclipse extras
      I installed subclispe SVN plugins

      I run the new Maven->Checkout Maven Projects from SCM wizard

      The SCM type combo box has no choices in it so the wizard is useless.

        Activity

        Hide
        Igor Fedorenko added a comment -

        We'll publish SCM integration when/if somebody volunteers to maintain and develop it. Raise your hand on m2e-dev@eclipse.org (subscribe as per http://m2eclipse.sonatype.org/project-information.html) if you are interested.

        For now you need to

        1. Checkout the project using cvs (or svn, or ...) from command line
        2. Import as Existing Maven Projects

        Show
        Igor Fedorenko added a comment - We'll publish SCM integration when/if somebody volunteers to maintain and develop it. Raise your hand on m2e-dev@eclipse.org (subscribe as per http://m2eclipse.sonatype.org/project-information.html ) if you are interested. For now you need to 1. Checkout the project using cvs (or svn, or ...) from command line 2. Import as Existing Maven Projects
        Hide
        Cefn Hoile added a comment -

        I'm not disagreeing with the accuracy or relevance of your response.

        However, in the absence of a maintainer there seems to be two ways for the project to go with this bug, and it's taken neither.

        a) fix the bug so that the wizard journey works
        b) remove the buggy wizard from the 'new project' journey in eclipse

        Leaving a non-functional wizard as part of the mainstream distribution is troublesome to say the least.

        As you say, there is a workaround, and it would be great to get someone to make this pathway functional, but until it is, it's best to remove the cruft of broken code rather than leave it there for people to waste their time trying to find the non-existent combination of eclipse features which will make it work.

        Show
        Cefn Hoile added a comment - I'm not disagreeing with the accuracy or relevance of your response. However, in the absence of a maintainer there seems to be two ways for the project to go with this bug, and it's taken neither. a) fix the bug so that the wizard journey works b) remove the buggy wizard from the 'new project' journey in eclipse Leaving a non-functional wizard as part of the mainstream distribution is troublesome to say the least. As you say, there is a workaround, and it would be great to get someone to make this pathway functional, but until it is, it's best to remove the cruft of broken code rather than leave it there for people to waste their time trying to find the non-existent combination of eclipse features which will make it work.

          People

          • Assignee:
            Unassigned
            Reporter:
            John Kenny
            Last Updated By:
            Cefn Hoile
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Date of First Response: