Uploaded image for project: 'Maven Project Info Reports Plugin'
  1. Maven Project Info Reports Plugin
  2. MPIR-280

Clarify that Web Access SCM link is not suitable for SCM checkout

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.7
    • 2.8
    • scm
    • None

    Description

      The details for the viewvc section say (for example):

      >>>
      Web Access

      The following is a link to the online source repository.

      http://svn.apache.org/viewvc/commons/proper/lang/trunk
      <<<

      This has been taken by some readers to imply that the URL is suitable for SVN client access, and there have been complaints on mailing lists when it does not work.

      It would be useful to clarify the text to reduce user frustration and unnecessary mailing list traffic.

      The text "The following is a link to the online source repository." applies equally to a proper SVN link. It does not indicate that URL is intended for Web Brower (HTTP) access only.

      The section header "Web Access" does not really help either, as "Web" is often used as a synonym for "Internet".

      I can see how readers who don't know about ViewVC could easily not notice that distinction.

      I suggest that the default text is changed as follows:

      report.scm.webaccess.title=Web Server (HTTP) Access
      report.scm.webaccess.url=
      The following is a link to a browsable version of the source repository.
      Please use the "Anonymous Access" or "Developer Access" URL if you want to check out the source using your SCM client.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            michael-o Michael Osipov
            sebb Sebb
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment