Maven Integration for Eclipse

Failing to update central index

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 0.9.6
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Linux, Kubuntu 8.04 KDE4
  • Number of attachments :
    0

Description

Today after updating the central index I noticed some error messages in the console:
9/10/08 4:37:24 PM EEST: Error on adding indexing context central; /home/joonas/workspace/.metadata/.plugins/org.maven.ide.eclipse/nexus/central/_9.fdt (No such file or directory)

I tried uninstalling the central index feature, removing the org.maven.ide.eclipse/nexus/central directory (which resulted redownloading the index, then the same issue again).

No idea how to fix this; no errors are reported while downloading the index (http://repo1.maven.org/maven2/.index/nexus-maven-repository-index.zip).. Could the index file be broken? Long exception trace was outputted to console running eclipse:

Exception in thread "Thread-6" org.apache.lucene.index.MergePolicy$MergeException: java.io.FileNotFoundException: /home/joonas/workspace/.metadata/.plugins/org.maven.ide.eclipse/nexus/central/_9.fdt (No such file or directory)
at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:271)
Caused by: java.io.FileNotFoundException: /home/joonas/workspace/.metadata/.plugins/org.maven.ide.eclipse/nexus/central/_9.fdt (No such file or directory)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
at org.apache.lucene.store.FSDirectory$FSIndexInput$Descriptor.<init>(FSDirectory.java:506)
at org.apache.lucene.store.FSDirectory$FSIndexInput.<init>(FSDirectory.java:536)
at org.apache.lucene.store.FSDirectory.openInput(FSDirectory.java:445)
at org.apache.lucene.index.FieldsReader.<init>(FieldsReader.java:75)
at org.apache.lucene.index.SegmentReader.initialize(SegmentReader.java:308)
at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:262)
at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:221)
at org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3099)
at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2834)
at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:240)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Joonas Koivunen added a comment -

Forgot to mention that I am using Eclipse Ganymede J2EE distribution, updated version.

Show
Joonas Koivunen added a comment - Forgot to mention that I am using Eclipse Ganymede J2EE distribution, updated version.
Hide
Permalink
Joonas Koivunen added a comment -

Having just done the same kind of (fresh) installation to Vista there's the same problem..

Show
Joonas Koivunen added a comment - Having just done the same kind of (fresh) installation to Vista there's the same problem..
Hide
Permalink
Eugene Kuleshov added a comment -

I confirmed that index published on central Maven repository is broken.

Show
Eugene Kuleshov added a comment - I confirmed that index published on central Maven repository is broken.
Hide
Permalink
Joonas Koivunen added a comment -

I have notified dev@maven.apache.org about this problem about 40min before this comment..

Show
Joonas Koivunen added a comment - I have notified dev@maven.apache.org about this problem about 40min before this comment..
Hide
Permalink
Martin Goldhahn added a comment -

After I reindexed the local repository the problem disappeared.

Show
Martin Goldhahn added a comment - After I reindexed the local repository the problem disappeared.
Hide
Permalink
Joonas Koivunen added a comment -

Seems that the index has been redone.. Just updated and it works.

Should there be a possibility to change what index file to use? It seems that central repo keeps older indexes too? Or even fallback to previous one automatically?

Show
Joonas Koivunen added a comment - Seems that the index has been redone.. Just updated and it works. Should there be a possibility to change what index file to use? It seems that central repo keeps older indexes too? Or even fallback to previous one automatically?
Hide
Permalink
Eugene Kuleshov added a comment -

I will add checks to make sure that broken index won't be installed.

Show
Eugene Kuleshov added a comment - I will add checks to make sure that broken index won't be installed.

People

  • Assignee:
    Unassigned
    Reporter:
    Joonas Koivunen
Vote (4)
Watch (6)

Dates

  • Created:
    Updated: