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-725

project-sensitive artifact index

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 1.1
  • Component/s: Indexer
  • Labels:
    None
  • Number of attachments :
    0

Description

Currently, m2e maintains list of repository indexes which is not related to repositories configured in settings.xml or repositories configured in projects pom.xml files. This can result in inconsistency between artifact index and maven artifact resolver, i.e. index can show artifacts not available during resolution or can miss artifacts that are in fact available. It would be nice if m2e artifact index was project sensitive and used repositories actually used to resolve project artifacts.

It would be also nice to warn users if some repositories used by workspace projects do not contain nexus indexes, and possible provide some guidelines on how to get a repository indexed.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MNGECLIPSE-944 Certain dependency source jars are not being downloaded

  • Critical - Crashes, loss of data, severe memory leak.
  • 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
Eugene Kuleshov added a comment - 08/Jul/08 5:32 PM

This would be really nice to have. Also note that by default there is only index for central repository and unless user adds some other index added to "Maven Indexes" view that corresponds to the index not listed in given project or sitting in an non active profile, index search won't show artifacts not available during resolution.

As for the missing index warning, it is currently being shown on the Maven console when index is being updated, either on startup or when index update is triggered manually.

Show
Eugene Kuleshov added a comment - 08/Jul/08 5:32 PM This would be really nice to have. Also note that by default there is only index for central repository and unless user adds some other index added to "Maven Indexes" view that corresponds to the index not listed in given project or sitting in an non active profile, index search won't show artifacts not available during resolution. As for the missing index warning, it is currently being shown on the Maven console when index is being updated, either on startup or when index update is triggered manually.
Hide
Permalink
Olivier Cailloux added a comment - 14/Feb/09 4:14 PM

Sorry for this "me 2" comment, but I'd like to explain why I think this is important feature to add. I hope it is useful.

As a beginner user of maven and m2eclipse, I found on a website instructions on adding a third-party index to get some artifacts (args4j). I added it to the m2eclipse index view, and wondered for a long time why m2eclipse was not downloading it, before figuring out that something has to be added to the project pom.xml. The error in m2eclipse console ("missing artifact") isn't helpful, and, for a beginner like me, this was really difficult to understand. Luckily Eugene Kuleshov helped me on the m2eclipse-user mailing list.

I think many other beginners might have the same problem... (Apart from that, I found m2eclipse very user-friendly and easy to understand.)

Show
Olivier Cailloux added a comment - 14/Feb/09 4:14 PM Sorry for this "me 2" comment, but I'd like to explain why I think this is important feature to add. I hope it is useful. As a beginner user of maven and m2eclipse, I found on a website instructions on adding a third-party index to get some artifacts (args4j). I added it to the m2eclipse index view, and wondered for a long time why m2eclipse was not downloading it, before figuring out that something has to be added to the project pom.xml. The error in m2eclipse console ("missing artifact") isn't helpful, and, for a beginner like me, this was really difficult to understand. Luckily Eugene Kuleshov helped me on the m2eclipse-user mailing list. I think many other beginners might have the same problem... (Apart from that, I found m2eclipse very user-friendly and easy to understand.)

People

  • Assignee:
    Unassigned
    Reporter:
    Igor Fedorenko
Vote (3)
Watch (3)

Dates

  • Created:
    08/Jul/08 4:11 PM
    Updated:
    14/Feb/09 4:14 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.