| Summary: | Maven plugin for eclipse doesn't replicate the index at central|http://repo1.maven.org/maven2 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Vijay Anand <ananvij> | ||||||||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||||||||
| Status: | CLOSED NOT_ECLIPSE | QA Contact: | |||||||||||
| Severity: | critical | ||||||||||||
| Priority: | P3 | CC: | igor | ||||||||||
| Version: | unspecified | ||||||||||||
| Target Milestone: | --- | ||||||||||||
| Hardware: | PC | ||||||||||||
| OS: | Windows 7 | ||||||||||||
| Whiteboard: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Vijay Anand
Created attachment 188535 [details]
add dependency dialog screenshot
I am not able to reproduce the problem using reasonably recent m2e 0.13.0, see attached screenshot. To help us narrow down the problem, can you verify if the problem is reproducible for you using m2e 0.13.0. You can install it from Eclipse 3.7 Indigo M5 repository, it is also available as part of 3.7M5 Java Eclipse distribution.
Created attachment 188536 [details]
0 finds on jglobus
with maven version 0.12.1.20110112-1712
will try with the version 13 Did try with 0.13.0.201102080807 and it gives me 0 hits. attached is the screen shot. Created attachment 188537 [details]
0 finds for jglobus in maven 0.13.0.201102080807
The same issue with latest maven
Is there any resolution on this? Can you check if Maven Repositories view shows any artifacts under org/jglobus? Created attachment 188944 [details] Global Repositories after rebuild I did a rebuild of the index on the global repositories. My initial bug was that I can find the repository on http://repo1.maven.org/maven2 but cannot see in the my global repository index on eclipse. I don't see the name as org/jglobus under Maven repositories I don't see the name as org/jglobus under Maven repositories Interesting... Normally, I use our corporate nexus server as mirrorOf=external:* in my settings.xml and the artifact is present both in Maven Repositories view and in Add Dependencies dialog. I am able to reproduce the problem once I removed mirror configuration from settings.xml. I have forwarded this question to maven index developers to see if they have a good explanation of this problem. Maven central repository index was outdated due to index mirror sync misconfiguration. The problem with index mirroring is solved now and I am able to see jglobus artifacts both in Repository View and in Add Dependency dialog. Do note that Maven central repository index is updated weekly, and the newly deployed artifacts only become available in the index after next index update. |