Eclipse Community Forums: M2T (model-to-text transformation)

Home » Modeling » M2T (model-to-text transformation) » Java Indexer running unnecessarily(Indexing directories not related to any project)

Show: Today's Messages :: Show Polls :: Message Navigator

Java Indexer running unnecessarily [message #635022]

Mon, 25 October 2010 12:50

Mark Hagan

Messages: 3
Registered: August 2009

Junior Member

I am running eclipse Galileo which is often very slow. I see in the following example event details in error log view which may be one contributing factor:-

"The Java indexing could not index V:/weblogic-10.3.2.0/modules/com.bea.core.repackaged.springf ramework.spring_1.0.0.0_2-5-3.jar|com/bea/core/repackaged/sp ringframework/transaction/annotation/Transactional.class. This .class file doesn't follow the class file format specification. Please report this issue against the .class file vendor"

This path is not on the build path or mentioned in any workspace project. Why is eclipse going through these dirs? Is there any way to stop it? I have many dirs on this V:\ drive that are not relevant to eclipse and I do not want eclipse wasting time indexing them.

Report message to a moderator

Re: Java Indexer running unnecessarily [message #635024 is a reply to message #635022]

Mon, 25 October 2010 12:52

Mark Hagan

Messages: 3
Registered: August 2009

Junior Member

Sorry this has been put in the wrong forum. I thought I was in JDT. Can this be moved there or do I have to repost?

Report message to a moderator

Re: Java Indexer running unnecessarily [message #635194 is a reply to message #635022]

Mon, 25 October 2010 22:31

Sebastian Zarnekow

Messages: 3118
Registered: July 2009

Senior Member

I guess this question was raised in the wrong newsgroup.

Am 25.10.10 14:50, schrieb Mark Hagan:
> I am running eclipse Galileo which is often very slow. I see in the
> following example event details in error log view which may be one
> contributing factor:-
>
> "The Java indexing could not index
> V:/weblogic-10.3.2.0/modules/com.bea.core.repackaged.springf
> ramework.spring_1.0.0.0_2-5-3.jar|com/bea/core/repackaged/sp
> ringframework/transaction/annotation/Transactional.class. This .class
> file doesn't follow the class file format specification. Please report
> this issue against the .class file vendor"
>
> This path is not on the build path or mentioned in any workspace
> project. Why is eclipse going through these dirs? Is there any way to
> stop it? I have many dirs on this V:\ drive that are not relevant to
> eclipse and I do not want eclipse wasting time indexing them.

Report message to a moderator

Re: Java Indexer running unnecessarily [message #635245 is a reply to message #635194]

Tue, 26 October 2010 07:42

Dani Megert

Messages: 3802
Registered: July 2009

Senior Member

Sebastian Zarnekow wrote:
> I guess this question was raised in the wrong newsgroup.
>
> Am 25.10.10 14:50, schrieb Mark Hagan:
>> I am running eclipse Galileo which is often very slow. I see in the
>> following example event details in error log view which may be one
>> contributing factor:-
>>
>> "The Java indexing could not index
>> V:/weblogic-10.3.2.0/modules/com.bea.core.repackaged.springf
>> ramework.spring_1.0.0.0_2-5-3.jar|com/bea/core/repackaged/sp
>> ringframework/transaction/annotation/Transactional.class. This .class
>> file doesn't follow the class file format specification. Please report
>> this issue against the .class file vendor"
>>
>> This path is not on the build path or mentioned in any workspace
>> project. Why is eclipse going through these dirs?
Eclipse is not going through directories. The JAR is most likely on your
build path. If not directly then indirectly via a MANIFEST.MF entry in
one of the directly referenced JARs.

Dani
>> Is there any way to
>> stop it? I have many dirs on this V:\ drive that are not relevant to
>> eclipse and I do not want eclipse wasting time indexing them.
>

Report message to a moderator

Re: Java Indexer running unnecessarily [message #635268 is a reply to message #635245]

Tue, 26 October 2010 08:47

Mark Hagan

Messages: 3
Registered: August 2009

Junior Member

Thanks Dani. Yes that's what it turned out to be. I stripped the build path right down and it seemed to perform a bit better with less errors in the log.

Report message to a moderator

Previous Topic:	[Acceleo] Can Acceleo support @text-explicit syntax ?
Next Topic:	[Acceleo 3 / Helios] Cannot lauch transformation

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 22:48:57 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter