Maven 1.x SCM Plugin
  1. Maven 1.x SCM Plugin
  2. MPSCM-52

scm:bootstrap fails on SVN project requiring username/password.

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5
    • Fix Version/s: 1.5
    • Labels:
      None
    • Environment:
      WinXP (SP2); 5.0 JVM
    • Number of attachments :
      0

      Description

      Trying to boostrap an SVN project, requiring a username/password does not appear to be working. Specifying the command-line below results in the output listed. Looking the plugin.jelly, I do not see where the username and/or password are being taken into consideration. Am I missing something?

      maven -Dmaven.proxy.host=proxy.host.com -Dmaven.proxy.port=80 -Dmaven.scm.url=scm:svn:http://svnserver/repos/myproject/trunk/ -Dmaven.scm.svn.module=mymodule -Dmaven.scm.username=u1 -Dmaven.scm.password=p1 scm:bootstrap
      __ __

      \/ __ Apache_ ___
        \/ / ` \ V / -) ' \ ~ intelligent projects ~
      _   _,_ _/___ _ _ v. 1.0.2

      build:start:

      scm:find-connection:
      [echo] Using connection: scm:svn:http://svnserver/repos/myproject/trunk/

      scm:checkout:
      [echo] Checking out scm:svn:http://svnserver/repos/myproject/trunk/
      [INFO] Working directory: C:\blah\target\checkout
      [INFO] Command line: svn checkout --non-interactive http://svnserver/repos/myproject
      /trunk/ checkout
      Provider message:
      The svn command failed.
      Command output:
      svn: PROPFIND request failed on '/repos/myproject/trunk'
      svn: PROPFIND of '/repos/myproject/trunk': authorization failed (http://svnserver)

      BUILD FAILED
      File...... C:\Documents and Settings\James F Bisotti\.maven\cache\maven-scm-plug
      in-1.5-beta-3\plugin.jelly
      Element... scm:checkout
      Line...... 110
      Column.... 167
      Error!
      Total time: 4 seconds

        Activity

        Hide
        Jamie Bisotti added a comment -

        Forgot to mention this is using 1.5-beta-3. Also when I use the command-line listed in the above output along with the --username and --password arguments, it works just fine.

        Show
        Jamie Bisotti added a comment - Forgot to mention this is using 1.5-beta-3. Also when I use the command-line listed in the above output along with the --username and --password arguments, it works just fine.
        Hide
        Brett Porter added a comment -

        I think this is fixed in SVN: can you check it out from http://svn.apache.org/repos/asf/maven/maven-1/branches/scm-1.5-branch
        and run maven plugin:install ?

        Show
        Brett Porter added a comment - I think this is fixed in SVN: can you check it out from http://svn.apache.org/repos/asf/maven/maven-1/branches/scm-1.5-branch and run maven plugin:install ?
        Hide
        Jamie Bisotti added a comment -

        Is the URL correct? I'm getting "Not Found" in my browser.

        Show
        Jamie Bisotti added a comment - Is the URL correct? I'm getting "Not Found" in my browser.
        Show
        Brett Porter added a comment - sorry... http://svn.apache.org/repos/asf/maven/maven-1/plugins/branches/scm-1.5-branch/ (missed plugins)
        Hide
        Jamie Bisotti added a comment -

        OK, I downloaded and built the 1.5-beta-4 code.

        Assuming I execute the command from C:\blah, I'm seeing the following:

        [INFO] Working directory: C:\blah\target\checkout

        From the documetation, I was thinking my code would end up in C:\blah\checkout. Is this a bug or am I just misundersanding things?

        Also, with C:\target\checkout being the "working" directory, the "svn checkout http://some.url checkout" command causes my code to eventually end up in C:\blah\checkout\checkout. However, scm:bootstrap is looking for project.xml in c:\blah\target\checkout; so, I am getting my code pulled, but the goal is failing.

        Show
        Jamie Bisotti added a comment - OK, I downloaded and built the 1.5-beta-4 code. Assuming I execute the command from C:\blah, I'm seeing the following: [INFO] Working directory: C:\blah\target\checkout From the documetation, I was thinking my code would end up in C:\blah\checkout. Is this a bug or am I just misundersanding things? Also, with C:\target\checkout being the "working" directory, the "svn checkout http://some.url checkout" command causes my code to eventually end up in C:\blah\checkout\checkout. However, scm:bootstrap is looking for project.xml in c:\blah\target\checkout; so, I am getting my code pulled, but the goal is failing.
        Hide
        Jamie Bisotti added a comment -

        Oops! I just rechecked the doco; looks like target/checkout is correct. However, I believe target/checkout/checkout is incorrect. FYI, the properties page actually lists "checkoutS" instead of "checkout".

        Show
        Jamie Bisotti added a comment - Oops! I just rechecked the doco; looks like target/checkout is correct. However, I believe target/checkout/checkout is incorrect. FYI, the properties page actually lists "checkoutS" instead of "checkout".
        Hide
        Brett Porter added a comment -

        I've verified this is working correctly in both cases

        Show
        Brett Porter added a comment - I've verified this is working correctly in both cases

          People

          • Assignee:
            Brett Porter
            Reporter:
            Jamie Bisotti
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: