Uploaded image for project: 'repository.jboss.org/nexus'
  1. repository.jboss.org/nexus
  2. NEXUS-93

Repository Routing for Fusesource Artifacts

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • None
    • MWES 2019-03-05, MWES 2019-03-19, MWES 2019-04-02, MWES 2019-04-16, MWES 2019-04-30, MWES 2019-05-14, MWES 2019-05-28

    Description

      Currently there is no routing set for Fusesource stuff which slows down artifact retrieval for their artifacts. I analyzed repositories and I suggest this rules.

      Group List of Repositories
      com.fusesource fs-releases, fs-snapshots, fs-subscriber-snapshot
      org.fusesource fs-beta, fs-maven2-legacy, fs-patches, fs-releases, fs-releases-internal, fs-maven2-all, fs-release-3rd-party, fs-releases-to-central, fs-snapshots, fs-subscriber, fs-subscriber-snapshot
      org.jboss fs-beta, fs-releases, fs-releases-internal, fs-snapshots
      io.fabric8 fs-beta, fs-releases, fs-releases-to-central, fs-snapshots
      io.hawt fs-beta, fs-releases, fs-snapshots

      Routing is explained here

      janstey, can you, please, have a look on list above, if you think it is correct? If I forgot something, some artifact would disappear from the group repositories.

      Attachments

        Activity

          People

            dhladky@redhat.com David Hladky
            dhladky@redhat.com David Hladky
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: