Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 0.0.10
-
Fix Version/s: 0.0.10
-
Component/s: None
-
Labels:None
-
Environment:eclipse.buildId=M20060629-1905
java.version=1.6.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments: -os win32 -ws win32 -arch x86
Description
Updated from 0.0.9 to 0.0.10. Now I get a NullPointerException after adding a new dependency. I have to do a manual console build and "Project -> Clean..." to workaround this.
18.02.07 15:06:24 CET: Downloading [sunsite.dk] -> http://mirrors.sunsite.dk/maven2/xalan/xalan/2.7.0/xalan-2.7.0.jar
18.02.07 15:06:37 CET: Downloaded [sunsite.dk] -> http://mirrors.sunsite.dk/maven2/xalan/xalan/2.7.0/xalan-2.7.0.jar
18.02.07 15:06:38 CET: Unable to read model from /MMArchive/pom.xml; java.lang.NullPointerException
Error log:
java.lang.NullPointerException
at org.apache.lucene.index.FieldsReader.doc(FieldsReader.java:88)
at org.apache.lucene.index.SegmentReader.document(SegmentReader.java:284)
at org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.<init>(Indexer.java:529)
at org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:246)
at org.maven.ide.eclipse.index.Indexer.addDocument(Indexer.java:342)
at org.maven.ide.eclipse.index.MavenRepositoryIndexManager.updateIndex(MavenRepositoryIndexManager.java:95)
at org.maven.ide.eclipse.embedder.TransferListenerAdapter.transferCompleted(TransferListenerAdapter.java:95)
at org.apache.maven.wagon.events.TransferEventSupport.fireTransferCompleted(TransferEventSupport.java:135)
at org.apache.maven.wagon.AbstractWagon.fireGetCompleted(AbstractWagon.java:364)
at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:230)
at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:182)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:80)
at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:436)
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:327)
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:283)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:182)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:70)
at org.maven.ide.eclipse.embedder.EclipseArtifactResolver.resolve(EclipseArtifactResolver.java:61)
at org.apache.maven.embedder.MavenEmbedder.resolve(MavenEmbedder.java:300)
at org.maven.ide.eclipse.embedder.ClassPathResolver.materializeArtifactPath(ClassPathResolver.java:224)
at org.maven.ide.eclipse.embedder.ClassPathResolver.resolveClasspathEntries(ClassPathResolver.java:145)
at org.maven.ide.eclipse.builder.Maven2Builder.updateClasspath(Maven2Builder.java:95)
at org.maven.ide.eclipse.builder.Maven2Builder.build(Maven2Builder.java:86)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:603)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:167)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:230)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:233)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:252)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:285)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:145)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:208)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Do you have more then one remote repository or declared mirrors in your settings.xml? I don't see /MMArchive/pom.xml in Maven central repository.
Can you reproduce that every time or it just happens once? If it happens every time, please attach test project and settings.xml that would allow to reproduce this issue.
I am not sure why command line build is needed. Project/Clean does trigger refresh of the Maven classpath container and you can also reindex local repository from the Window / Preferences / Maven.