Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-218

Modify the repository routes to be assigned to a group

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0-beta
    • Fix Version/s: 1.0-beta
    • Component/s: None
    • Labels:
      None

      Description

      Repository routes are global, and are applied to all groups.

      This prevents fine tuning, and / or confuses users, ie. when they add new reposes and groups and forget to update the repo routes too, which by default affects the newly created reposes and groups too.

      Typical example (we had questions about those on user lists already): user have an inclusive route for "maven" (ie. /org/apache/maven/.*) reposes, initially with "central" and "apache snapshots" as members. The user later creates a new repo for locally built maven artifacts (because they are customizing plugins for example that will go upstream to maven project) and creates a new hosted repo and new group for those projects.

      Finally, the user is stunned, that deployment is fine (it goes directly to new hosted repo), but the developers cannot get dependencies from the new repository over the newly created group. This is because the new group is also affected by "global" inclusive route that contains "central" and "apache snapshots" only.

      The current solution: update the inclusive route and add the new repo too, but it may (actually it is) affecting all other consumers of that Nexus instance!

      The repo routes should be "assignable" to single group only, but also have an option for "*" (meaning ALL, behaving just like now).

      On upgrade, all repo route should have set "*" for repoGroupId, to prevent unintentional behaviour change.

        Attachments

          Activity

            People

            Assignee:
            cstamas Tamás Cservenák
            Reporter:
            cstamas Tamás Cservenák
            Last Updated By:
            Peter Lynch Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4h Original Estimate - 4h
                4h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 6h
                6h

                  tigCommentSecurity.panel-title