jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
Maven Integration for Eclipse
  • Maven Integration for Eclipse
  • MNGECLIPSE-1033

allow to use non-unique index ids

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 0.9.6
  • Fix Version/s: 0.9.8
  • Component/s: Indexer
  • Labels:
    None
  • Number of attachments :
    0

Description

  • added a new index and pointed it at one nexus group. The context provided by nexus is "public-merged".
  • then edited the existing Central index url to point at another nexus instance.
  • clicked retrieve context and it also said public-merged.
  • When i saved it, the central one simply disappeared.

What if i really want both indexes? I don't have control all the time of the context used on the remote url so m2e should be able to handle this.

Nexus deals with it by changing the context after it's downloaded before attempting to merge them together.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
No work has yet been logged on this issue.

People

  • Assignee:
    Rich Seddon
    Reporter:
    Brian Fox
Vote (0)
Watch (0)

Dates

  • Created:
    03/Nov/08 3:48 PM
    Updated:
    18/Feb/09 1:09 PM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.