- This topic has 13 replies, 5 voices, and was last updated 15 years, 5 months ago by
support-joy.
-
AuthorPosts
-
I have been using MyEclipse for several years across different versions. For the 1st time, its code completion feature stopped working last week. When I type a period after a package/class name, class/method names no longer automatically appear. I examined the settings under Window -> preference -> Java -> Editor -> Content assist, they are fine and unchanged. I tried shortcut (clt + space, and others) after a period, the message displayed is “not default proposals” or “no template proposals”.
I uninstalled and reinstalled MyEclipse 6.6, and installed Myeclipse 7.0, both versions do not have code completion when I open any of my projects in my (old) workspace. But both versions have code completion in a new workspace if I create one. So the difference is in the workspace. I compared the files in the old and new workspaces, There is only a .metadata dir in the new workspace, and files in that dir (.lok, .log, version.ini,) are practically empty. What is the function/format of .metadata? Is it has something to do with code completion?
It is such a pain without this code completion. Please help me fix this.
I know you want to know my installation summary, here it is:
*** Date:
Sunday, December 14, 2008 11:55:15 PM CST** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_11*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.6.0
Build id: 6.6.0-20081015*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 6.6.0
Build id: 6.6.0-20081015Eclipse Platform
Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800Eclipse RCP
Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800Eclipse Java Development Tools
Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800Eclipse Plug-in Development Environment
Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800Eclipse Project SDK
Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800Eclipse Graphical Editing Framework
Version: 3.3.2.v20080129
Build id: 20080221-1602Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\development\apps\MyEclipse 6.6\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\development\apps\MyEclipse 6.6\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\development\apps\MyEclipse 6.6\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
1fc_74
-clean
-vm
C:\development\apps\MyEclipse 6.6\jre\bin\javaw.exeDecember 15, 2008 at 12:04 am #292090Also I found the following in the error log. I can paste whole error log, but it is very long.
!ENTRY org.maven.ide.eclipse 4 0 2008-12-14 17:19:44.636
!MESSAGE Error on adding indexing context central
!STACK 0
java.io.FileNotFoundException: C:\development\data\eclipse_dev\.metadata\.plugins\org.maven.ide.eclipse\nexus\central\_9.fdt (The system cannot find the file specified)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.<init>(Unknown Source)
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:197)
at org.apache.lucene.index.MultiSegmentReader.<init>(MultiSegmentReader.java:55)
at org.apache.lucene.index.DirectoryIndexReader$1.doBody(DirectoryIndexReader.java:75)
at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:636)
at org.apache.lucene.index.DirectoryIndexReader.open(DirectoryIndexReader.java:63)
at org.apache.lucene.index.IndexReader.open(IndexReader.java:209)
at org.apache.lucene.index.IndexReader.open(IndexReader.java:192)
at org.sonatype.nexus.index.context.DefaultIndexingContext.getIndexReader(DefaultIndexingContext.java:341)
at org.sonatype.nexus.index.context.DefaultIndexingContext.getIndexSearcher(DefaultIndexingContext.java:358)
at org.sonatype.nexus.index.context.DefaultIndexingContext.checkAndUpdateIndexDescriptor(DefaultIndexingContext.java:201)
at org.sonatype.nexus.index.context.DefaultIndexingContext.prepareIndex(DefaultIndexingContext.java:166)
at org.sonatype.nexus.index.context.DefaultIndexingContext.<init>(DefaultIndexingContext.java:141)
at org.sonatype.nexus.index.DefaultNexusIndexer.addIndexingContext(DefaultNexusIndexer.java:115)
at org.maven.ide.eclipse.internal.index.NexusIndexManager.addIndexingContext(NexusIndexManager.java:120)
at org.maven.ide.eclipse.internal.index.NexusIndexManager.addIndex(NexusIndexManager.java:111)
at org.maven.ide.eclipse.MavenPlugin.loadIndexConfiguration(MavenPlugin.java:245)
at org.maven.ide.eclipse.MavenPlugin.start(MavenPlugin.java:174)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:260)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:417)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:189)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:340)
at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:37)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:405)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:136)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:970)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:260)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:417)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:189)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:340)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:408)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:289)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1269)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:160)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:788)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
at org.eclipse.jdt.internal.core.JavaModelManager$2.run(JavaModelManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.jdt.internal.core.JavaModelManager$CompilationParticipants.getCompilationParticipants(JavaModelManager.java:248)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.initializeBuilder(JavaBuilder.java:574)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:166)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:624)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:166)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:197)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:246)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:302)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:334)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:137)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)December 15, 2008 at 1:34 pm #292141Have I posted the question in the right forum ?
December 16, 2008 at 6:23 am #292179
Loyal WaterMemberYou can try using the -clean to try and fix this issue:-
https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/Does code complete work with new projects in the old workspace?
December 16, 2008 at 8:45 am #292204
GregMemberHere is another thought. For some unknown reason the java content assist proposals will turn themselves off. If you can no longer get them, do this:
1. Go to Window > Prefs > Java > Editor > Content Assist > Advanced
2. Select the “Restore Defaults” button at the bottom right of the pageIf any of the proposal kinds had been turned off the restore defaults will restore them.
December 16, 2008 at 10:10 am #292239I tried to use the -clean argument and it did not fix it. On a second thought I have uninstalled and reinstalled MyEclipse 6.6. If that did not clean well enough, then the MyEclipse 7.0 is a brand new installation.
Code completion does NOT work with new project in the old workspace. However it works in new workspace with imported projects. But when I imported projects over to the new workspace, no files are moved over to the new workspace dir, the IDE still working on the files in the old dir, so it must be something in .metadata dir remembered the project information. In the new workspace, code completion works but code would not compile.
Can you consult your dev team ? Thanks!
@support-nipun wrote:
You can try using the -clean to try and fix this issue:-
https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/Does code complete work with new projects in the old workspace?
December 16, 2008 at 10:18 am #292243It was in the first few things I tried, just on the safe side I tried it again. It did nothing. Although code completion is not working, but the error checking is working. If I mistyping a method name, it will error mark that line.
@support-greg wrote:
Here is another thought. For some unknown reason the java content assist proposals will turn themselves off. If you can no longer get them, do this:
1. Go to Window > Prefs > Java > Editor > Content Assist > Advanced
2. Select the “Restore Defaults” button at the bottom right of the pageIf any of the proposal kinds had been turned off the restore defaults will restore them.
December 16, 2008 at 10:57 am #292253I have not heard explanation of the role of .metadata dir. But seems like the setting in .metadata/.plugins/org.eclipse.core.resources/.projects dir are critical.
December 16, 2008 at 11:55 am #292265
GregMemberThe preferences are stored in the .metadata folder, so it is used as the backing for the preference storage. Does restore defaults cause the content assist to begin working again?
December 16, 2008 at 1:25 pm #292285No. It is strang.
@support-greg wrote:
Does restore defaults cause the content assist to begin working again?
December 16, 2008 at 2:46 pm #292293
GregMemberCould you paste your entire error log here? We can see if there are any errors that are related to content assist proposals not working.
December 18, 2008 at 8:32 am #292417I have sent you my error log as private message yesterday, let me know if you need more information. Thanks.
@support-greg wrote:Could you paste your entire error log here? We can see if there are any errors that are related to content assist proposals not working.
January 23, 2010 at 9:54 pm #305567
LitreMemberThis message has not been recovered.
January 25, 2010 at 12:23 am #305578
support-joyMemberThis message has not been recovered.
-
AuthorPosts