Uploaded image for project: 'Archiva (Retired)'
  1. Archiva (Retired)
  2. MRM-462

separate configuration of managed repositories from remote repositories

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 1.0-beta-1
    • 1.0-beta-2
    • Web Interface
    • None

    Description

      the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).

      1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
      2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
      3) I think we should consider separating them into different lists in the configuration again.

      Attachments

        Issue Links

          Activity

            People

              brett Brett Porter
              brett Brett Porter
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: