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)
  • Maven 2 & 3
  • MNG-1974

Improve repository searching for artifacts

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 2.0.2
  • Fix Version/s: Issues to be reviewed for 3.x
  • Component/s: Artifacts and Repositories
  • Labels:
    None
  • Complexity:
    Intermediate

Description

Currently, if there are multiple repositories defined in poms and or settings, each time an artifact is retreived, it searches through the list, displaying warnings that couldn't be found for each repository. There are 2 enhancements that I can think of:

1. Don't print warning when it can't be found in the repository, unless it can't be found anywhere. This is just a neusance and clutters the screen. If it printed the url when it actually found it, I would be able to see where it came from and that's more than sufficient.
2. When looking for a jar, try looking where you just found the pom. I can't think of a good reason why it would be good to grab a jar from a repo different than where we found the pom. In this case, it just throws up a bunch more warnings when it should know where exactly to find the jar.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-2098 Artifact resolver incorrectly selects repository which doesn't contain the selected version

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-2648 Repeated message "[WARNING] Unable to get resource from repository ... "

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MNG-2823 More control over what WARNING messages are displayed

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Micah Whitacre added a comment - 13/Jun/07 12:56 PM

The second complaint seems similar to this issue.

Show
Micah Whitacre added a comment - 13/Jun/07 12:56 PM The second complaint seems similar to this issue.
Hide
Permalink
Micah Whitacre added a comment - 13/Jun/07 12:56 PM

The second complaint is covered by this issue.

Show
Micah Whitacre added a comment - 13/Jun/07 12:56 PM The second complaint is covered by this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Brian Fox
Vote (6)
Watch (6)

Dates

  • Created:
    17/Jan/06 2:13 PM
    Updated:
    13/Dec/08 6:34 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.