_id
stringlengths 36
36
| bug_id
int64 1
425k
| description
stringlengths 1
373k
⌀ | bug_severity
stringclasses 7
values | bug_status
stringclasses 3
values | resolution
stringclasses 8
values |
|---|---|---|---|---|---|
{'$oid': '52e9c14c54dc1c25ebdc0d15'} | 62,130 | I have javaw.exe.manifest in my jdk\bin directory that causes window toolbar
to be rendered little taller. The perspective toolbar wraps, when there is no
enough space to show all perspective buttons. The second line of the toolbar
is partially visible, which does not look nice. I will attach a screen shot.
BTW: despite looking bad it is a very convenient feature. | minor | RESOLVED | FIXED |
{'$oid': '52e9c14c54dc1c25ebdc0d16'} | 62,133 | After the DnD failure (as reported in other bugs), I use the Publish action to
publish the features to the site.
Initially I had two features, so I went to the source page and removed one of
them.
Later, when I wanted to save the site.xml, the file never gets saved, it still
has the * in the editor title, and there is no log produced. | major | RESOLVED | FIXED |
{'$oid': '52e9c14c54dc1c25ebdc0d17'} | 62,137 | Images
- need to recap the images and use GIF format (jpg format
does not show up properly in the eclipse help)
TOC & Topic titles need to match
TOC Title
Starting and stopping a trace Starting and stopping trace | minor | CLOSED | FIXED |
{'$oid': '52e9c14c54dc1c25ebdc0d18'} | 62,139 | Suggestions:
A) Restructure TOC to provide a clear user goal
e.g.
Hyades Statistical Console
Overview of the Hyades Statistical Console
Monitoring (machine?) performance
Creating a performance monitoring agent(current topic: Perfmon Launch
Configuration)
Observing data in a statistical data view
Creating a performance trace
Creating a StatCon file for a performance trace
Configuring performance objects
Starting and stopping a trace
Viewing a statistical model
Reference
Statistical console graphs and tables
B) May want to have an overview topic to explain
what the user can accomplish using the statcon & perfmon agent,
and the steps to get there,
e.g. Monitoring machine performance topic
with the following steps:
1. create perfmon agent
2. observing data in stat view
3. creating perf trace
4. configuring objects
5. analyzing data, etc..
C) Within each step, you may want to list a link to the prerequiste,
for example, in the topic Observing Data in statistical view,
you should list a prerequisite topic: Creating a perfmon agent.
Please let me know if you have any questions. | normal | CLOSED | FIXED |
{'$oid': '52e9c14c54dc1c25ebdc0d19'} | 62,138 | 1. Launch StartStop
2. After first prompt Detach
3. Hit enter to continue.
JVM crashes in piAgent. | major | CLOSED | FIXED |
{'$oid': '52e9c14c54dc1c25ebdc0d1a'} | 62,140 | Build M8
After changing a .cvsignore file in a text editor outside of eclipse the
following error occurs when trying to synchronize. This is even after trying to
do an "Override and update".
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource is out of sync
with the file system: /VisualPACS/.cvsignore.
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:484)
at org.eclipse.core.internal.resources.File.getContents(File.java:251)
at org.eclipse.core.internal.resources.File.getContents(File.java:241)
at
org.eclipse.team.internal.ccvs.core.util.SyncFileWriter.readLines(SyncFileWriter.java:455)
at
org.eclipse.team.internal.ccvs.core.util.SyncFileWriter.readCVSIgnoreEntries(SyncFileWriter.java:267)
at
org.eclipse.team.internal.ccvs.core.resources.SessionPropertySyncInfoCache.cacheFolderIgnores(SessionPropertySyncInfoCache.java:70)
at
org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.cacheFolderIgnores(EclipseSynchronizer.java:1068)
at
org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.isIgnored(EclipseSynchronizer.java:395)
at
org.eclipse.team.internal.ccvs.core.resources.EclipseResource.isIgnored(EclipseResource.java:126)
at
org.eclipse.team.internal.ccvs.core.resources.EclipseFolder.members(EclipseFolder.java:54)
at
org.eclipse.team.internal.ccvs.core.client.FileStructureVisitor.visitFolder(FileStructureVisitor.java:73)
at
org.eclipse.team.internal.ccvs.core.resources.EclipseFolder.accept(EclipseFolder.java:133)
at
org.eclipse.team.internal.ccvs.core.client.AbstractStructureVisitor.visit(AbstractStructureVisitor.java:255)
at
org.eclipse.team.internal.ccvs.core.client.SyncUpdate.sendFileStructure(SyncUpdate.java:28)
at
org.eclipse.team.internal.ccvs.core.client.Update.sendLocalResourceState(Update.java:82)
at
org.eclipse.team.internal.ccvs.core.client.Command.doExecute(Command.java:408)
at
org.eclipse.team.internal.ccvs.core.client.Update.doExecute(Update.java:202)
at
org.eclipse.team.internal.ccvs.core.client.Command$1.run(Command.java:337)
at
org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.run(EclipseSynchronizer.java:1403)
at
org.eclipse.team.internal.ccvs.core.resources.EclipseResource$2.run(EclipseResource.java:268)
at
org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1559)
at
org.eclipse.team.internal.ccvs.core.resources.EclipseResource.run(EclipseResource.java:265)
at
org.eclipse.team.internal.ccvs.core.client.Command.execute(Command.java:349)
at
org.eclipse.team.internal.ccvs.core.resources.RemoteFolderTreeBuilder.fetchDelta(RemoteFolderTreeBuilder.java:627)
at
org.eclipse.team.internal.ccvs.core.resources.RemoteFolderTreeBuilder.fetchDelta(RemoteFolderTreeBuilder.java:222)
at
org.eclipse.team.internal.ccvs.core.resources.RemoteFolderTreeBuilder.buildTree(RemoteFolderTreeBuilder.java:187)
at
org.eclipse.team.internal.ccvs.core.resources.RemoteFolderTreeBuilder.buildRemoteTree(RemoteFolderTreeBuilder.java:159)
at
org.eclipse.team.internal.ccvs.core.resources.CVSWorkspaceRoot.getRemoteTree(CVSWorkspaceRoot.java:450)
at
org.eclipse.team.internal.ccvs.core.syncinfo.CVSResourceVariantTree.fetchVariant(CVSResourceVariantTree.java:95)
at
org.eclipse.team.core.variants.AbstractResourceVariantTree.refresh(AbstractResourceVariantTree.java:107)
at
org.eclipse.team.core.variants.AbstractResourceVariantTree.refresh(AbstractResourceVariantTree.java:67)
at
org.eclipse.team.core.variants.ResourceVariantTreeSubscriber.refresh(ResourceVariantTreeSubscriber.java:153)
at
org.eclipse.team.core.variants.ResourceVariantTreeSubscriber.refresh(ResourceVariantTreeSubscriber.java:123)
at
org.eclipse.team.ui.synchronize.subscribers.RefreshSubscriberJob.runInWorkspace(RefreshSubscriberJob.java:185)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:37)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62)
!SUBENTRY 3 org.eclipse.core.resources 4 274 May 13, 2004 12:06:16.547
!MESSAGE Resource is out of sync with the file system: /VisualPACS/.cvsignore. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c14c54dc1c25ebdc0d1b'} | 62,141 | The UI should be displaying the option categories in the same order they are
defined in the plugin manifest. When a change was made to support forward-
referencing in the XML file, the categories were stored in a map that hashed
them, so they are returned in an arbitrarily different order than they were
added to the map. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14c54dc1c25ebdc0d1c'} | 62,143 | JDT uses at least 3 threads: All Types Caching, JavaReconciler, and Java
Indexer. For performance monitoring and profiling purposes, these should
be moved to the core jobs facility.
Currently, the threads run in the background and make calls to
Display.asyncExec. This makes their behavior difficult to track. If you
really need access to the UI from these threads, use a UI job. | normal | RESOLVED | NDUPLICATE |
{'$oid': '52e9c14c54dc1c25ebdc0d1e'} | 62,135 | This bug only appears in the Korean version of Windows 2k3. English win2k3 in
a korean locale is fine.
Reporter: Tony Liu
OS: windows 2003 Standard Edition(KOREAN version)
Language: KOR
Build level: IES20040506
JDK Version: IBM JDK 1.4.2 Beta
Test case #:Hyades05
Summary: Error message be shown in the Err log view .
Steps to recreate problem:
1- From the workbench main menu select "File->Import" a selection wizard page
will open. Select "Log File" and click "Next", the "Import Log" wizard opens..
2- Click "Add", the "Add Log File" dialog opens
3- Select "Apache Http Access Log" for the type of the log file
4- On the Host page of the log properties tab folder select "localhost:10002".
5- On the Details page browse for the "Access log file path" and select the
provided test log file apache_access.log.
6- Click "OK" to close the dialog, the access log will be added to the current
log set to be imported.
7- Repeat steps 2 to 6 selecting in step 3 "Apache Http Error Log" and in step
5 the provided test log file apache_error.log.
8- The two test log files are added to the default log set , click finish to
import them.
9- Verfiy the log files are showing up in the Log Navigator.
10- Selete both log files, right click and select "Save" to save both log files.
11- Close the workbench.
12- Restart the workbench.
<<Error>>
Have error messages be showed in the Err log view.
(hyades05errlog.jpg)
<<Expected Result>>
No error messages be shown in the Err log view. | normal | CLOSED | INVALID |
{'$oid': '52e9c14c54dc1c25ebdc0d1f'} | 62,144 | I just installed Eclipse 3.0 M8 (build 200403261517) w/ CDT 2.0 M8
and wanted to create a new C++ project as described in the CDT FAQ, C/C++
Project Creation, 1. Creating a simple Managed C++ Project -- "Hello World on a
Windows Platform". But there is no C++ project entry to select.
If right-click in C++Projects and select "Other..." and "Show allWizards" is
checked-in I have the possibility to create a new C++ class but it will result
in more java NullException in the logs.
Here's the output of .metadata/.log after two attempts to create a C++ project:
!SESSION May 13, 2004 13:46:19.10 ----------------------------------------------
java.version=1.4.1_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
!ENTRY org.eclipse.ui 4 4 May 13, 2004 13:46:19.11
!MESSAGE Unhandled event loop exception
!ENTRY org.eclipse.ui 4 0 May 13, 2004 13:46:19.11
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at org.eclipse.cdt.ui.wizards.NewClassWizardPage.isSelectionCPP(Unknown Source)
at org.eclipse.cdt.ui.wizards.NewClassWizardPage.<init>(Unknown Source)
at org.eclipse.cdt.ui.wizards.NewClassWizard.addPages(Unknown Source)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:466)
at org.eclipse.jface.window.Window.create(Window.java:350)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:859)
at
org.eclipse.ui.internal.ide.NewWizardShortcutAction.run(NewWizardShortcutAction.java:96)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:550)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:502)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:435)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:939)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1953)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1726)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1562)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1536)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:257)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:139)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:277)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:239)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676)
!ENTRY org.eclipse.ui 4 4 May 13, 2004 13:46:28.548
!MESSAGE Unhandled event loop exception
!ENTRY org.eclipse.ui 4 0 May 13, 2004 13:46:28.549
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at org.eclipse.cdt.ui.wizards.NewClassWizardPage.isSelectionCPP(Unknown Source)
at org.eclipse.cdt.ui.wizards.NewClassWizardPage.<init>(Unknown Source)
at org.eclipse.cdt.ui.wizards.NewClassWizard.addPages(Unknown Source)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:466)
at org.eclipse.jface.window.Window.create(Window.java:350)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:859)
at
org.eclipse.ui.internal.ide.NewWizardShortcutAction.run(NewWizardShortcutAction.java:96)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:550)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:502)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:435)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:939)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1953)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1726)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1562)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1536)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:257)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:139)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:277)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:239)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676)
!SESSION May 13, 2004 13:53:40.932 ---------------------------------------------
java.version=1.4.1_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
!ENTRY org.eclipse.core.runtime 2 0 May 13, 2004 13:53:40.933
!MESSAGE Legacy plug-in "org.eclipse.core.filebuffers" must not be automatically
activated on startup. This is probably caused by a previous crash in Eclipse.
!ENTRY
reference:file:/usr/local/eclipse/plugins/org.eclipse.core.filebuffers_3.0.0/ 0
0 May 13, 2004 13:53:40.934
!MESSAGE FrameworkEvent.ERROR
!STACK 0
org.osgi.framework.BundleException: Exception in
org.eclipse.core.internal.compatibility.PluginActivator.start()
at
org.eclipse.osgi.framework.internal.core.BundleContext.startActivator(BundleContext.java:1009)
at
org.eclipse.osgi.framework.internal.core.BundleContext.start(BundleContext.java:971)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:404)
at org.eclipse.osgi.framework.internal.core.Bundle.resume(Bundle.java:377)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:971)
at
org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles(StartLevelImpl.java:565)
at
org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL(StartLevelImpl.java:479)
at
org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel(StartLevelImpl.java:269)
at
org.eclipse.osgi.framework.internal.core.StartLevelImpl.dispatchEvent(StartLevelImpl.java:439)
at
org.eclipse.osgi.framework.eventmgr.ListenerList.dispatchEvent(ListenerList.java:135)
at
org.eclipse.osgi.framework.eventmgr.EventThread$EventThreadItem.dispatchEvent(EventThread.java:59)
at org.eclipse.osgi.framework.eventmgr.EventThread.run(EventThread.java:118)
Nested exception:
org.osgi.framework.BundleException: Legacy plug-in
"org.eclipse.core.filebuffers" must not be automatically activated on startup.
This is probably caused by a previous crash in Eclipse.
at
org.eclipse.core.internal.compatibility.PluginActivator.ensureNormalStartup(PluginActivator.java:61)
at
org.eclipse.core.internal.compatibility.PluginActivator.start(PluginActivator.java:45)
at
org.eclipse.osgi.framework.internal.core.BundleContext$1.run(BundleContext.java:992)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContext.startActivator(BundleContext.java:988)
at
org.eclipse.osgi.framework.internal.core.BundleContext.start(BundleContext.java:971)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:404)
at org.eclipse.osgi.framework.internal.core.Bundle.resume(Bundle.java:377)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:971)
at
org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles(StartLevelImpl.java:565)
at
org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL(StartLevelImpl.java:479)
at
org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel(StartLevelImpl.java:269)
at
org.eclipse.osgi.framework.internal.core.StartLevelImpl.dispatchEvent(StartLevelImpl.java:439)
at
org.eclipse.osgi.framework.eventmgr.ListenerList.dispatchEvent(ListenerList.java:135)
at
org.eclipse.osgi.framework.eventmgr.EventThread$EventThreadItem.dispatchEvent(EventThread.java:59)
at org.eclipse.osgi.framework.eventmgr.EventThread.run(EventThread.java:118) | normal | RESOLVED | FIXED |
{'$oid': '52e9c14c54dc1c25ebdc0d21'} | 62,146 | It is slightly embarrasing for PDE to provide templates that generate obsolete
code i.e. code that has OSGi deprecation warnings or use runtime
compatibility. We should systematically go over all the 3.0 templates and make
sure they are good OSGi citizens in every way. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14c54dc1c25ebdc0d22'} | 62,147 | build I20040513-1200
- started on the new build
- it was taking a while
- did a Ctrl+Break in the console
I don't have -refresh specified on the command line, nor did I check the refresh
option in the Startup pref page.
Saw:
"main" prio=7 tid=0x00234d50 nid=0x800 runnable [6e000..6fc3c]
at java.io.WinNTFileSystem.list(Native Method)
at java.io.File.list(File.java:915)
at
org.eclipse.core.internal.localstore.UnifiedTree.getLocalList(UnifiedTree.java:313)
at
org.eclipse.core.internal.localstore.UnifiedTree.addChildren(UnifiedTree.java:94)
at
org.eclipse.core.internal.localstore.UnifiedTree.addNodeChildrenToQueue(UnifiedTree.java:204)
at
org.eclipse.core.internal.localstore.UnifiedTree.accept(UnifiedTree.java:76)
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:615)
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:602)
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:646)
at
org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:595)
at
org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1219)
at org.eclipse.core.internal.resources.Workspace.open(Workspace.java:1610)
at
org.eclipse.core.resources.ResourcesPlugin.startup(ResourcesPlugin.java:325)
at
org.eclipse.core.internal.compatibility.PluginActivator.start(PluginActivator.java:49)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:958)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:954)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:937)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:415)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:298)
at
org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:114)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.requireClass(BundleLoader.java:333)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findRequiredClass(BundleLoader.java:911)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:396)
at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
- locked <0x111f34e0> (a
org.eclipse.core.runtime.adaptor.EclipseClassLoader)
at
org.eclipse.ui.internal.ide.model.WorkbenchAdapterFactory.<init>(WorkbenchAdapterFactory.java:26)
at
org.eclipse.ui.internal.ide.model.WorkbenchAdapterBuilder.registerAdapters(WorkbenchAdapterBuilder.java:33)
at
org.eclipse.ui.internal.ide.IDEWorkbenchAdvisor.initialize(IDEWorkbenchAdvisor.java:159)
at
org.eclipse.ui.application.WorkbenchAdvisor.internalBasicInitialize(WorkbenchAdvisor.java:165)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:777)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1301)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:243)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:298)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:249)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:269)
at org.eclipse.core.launcher.Main.run(Main.java:722)
at org.eclipse.core.launcher.Main.main(Main.java:706) | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c14d54dc1c25ebdc0d24'} | 62,150 | I have a PRIVATE static method in some class and several references to it in
the same class.
Then I retype PUBLIC instead of PRIVATE in this static method declaration.
After that I'm doing a "Move static method" refactoring to put this static
method into the newly created empty top-level class.
The method moves OK, but the refences located in the original file were NOT
UPDATED. It expected that the method call must be preceded with the class name
where the method was moved and a colon. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c14d54dc1c25ebdc0d25'} | 62,152 | normal | RESOLVED | WORKSFORME |
|
{'$oid': '52e9c14d54dc1c25ebdc0d26'} | 62,154 | Using build 200405131200, sometimes the fast view gets a size of 0, and it looks
like it doesn't open anymore when it does open but with a size of 0. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14d54dc1c25ebdc0d27'} | 62,155 | While updating WSAD v5.1.1 (Eclipse 2.1.3) received an error message:
You cannot install in the site C:/WSAD/wstools/eclipse. It is considered non
updatable.
The error message needs to be self-explanatory so that the User can correct the
issue. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14d54dc1c25ebdc0d28'} | 62,136 | Hi,
I know that what now follows will sound quite annoying but I tested itas
painstaking as I could and my spare time allows.
I use eclipse m8 and for the demonstration emf is needed (I used 0408)
The problem is that the attached plugins both run well in runtime
environment.
after export > deploy the plugins with pde, the plugins in work.zip will run
after installing them to a fresh installed eclipse. the plugins in fail.zip will
fail with NoClassDefFoundError.
both plugins contain the same code except using other plugin names and
packagename (fail.zip has longer names). Also all other artifacts like
plugin.xml or .project differ only that way.
the code of the plugins is complete emf generated. you can reproduce building
the code by taking the genconf.ecore at src/model dir of one of the main plugins.
I tried this for several naming variants and it looks like the longer one fail,
but I can't exactly say how long they have to be.
I also tried to vary the build option which not change the effects.
To reproduce:
1. clean eclipse (deleting .metadata in ws, deleting configuration)
2. istall working.zip (three plugins)
3. import the test project (test.zip)
4. double click simple.genconf
5. the editor pops up
6. do 1. - 4. for fail.zip
7. an error occurs (see attached .log)
Again, I know this seems to be really odd and I'm still seeking for mistakes I
made,but trying to reproduce shouldn't take to much time for you following the
list above. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14d54dc1c25ebdc0d29'} | 62,151 | CDT 200405121551
Eclipse 200405121200
Not easily reproduced, but the screen cap doesn't lie.
I have come across this on Windows as well. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c14d54dc1c25ebdc0d2a'} | 62,153 | I200405131200
After a perspective switch, there is a chevron on the toolbar containing the
perspective buttons indicating that there are more available. However, if I
resize the cbanner's curve to show more or less of the perspective bar, I lose
the chevron. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c14d54dc1c25ebdc0d2b'} | 62,156 | build I20040513-1200
While deleting some projects in my workspace, I saw the following get logged:
Java Model Exception: Java Model Status [<project root> [in Foo] does not exist.]
at
org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:562)
at
org.eclipse.jdt.internal.core.PackageFragmentRoot.buildStructure(PackageFragmentRoot.java:169)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:183)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:573)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:310)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:296)
at
org.eclipse.jdt.internal.core.PackageFragmentRoot.getKind(PackageFragmentRoot.java:542)
at
org.eclipse.jdt.ui.actions.OrganizeImportsAction.hasSourceFolders(OrganizeImportsAction.java:258)
at
org.eclipse.jdt.ui.actions.OrganizeImportsAction.isEnabled(OrganizeImportsAction.java:241)
at
org.eclipse.jdt.ui.actions.OrganizeImportsAction.selectionChanged(OrganizeImportsAction.java:154)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchSelectionChanged(SelectionDispatchAction.java:200)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.selectionChanged(SelectionDispatchAction.java:195)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:159)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:607)
at org.eclipse.core.runtime.Platform.run(Platform.java:668)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:157)
at
org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:1268)
at
org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1001)
at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:356)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.handleInvalidSelection(PackageExplorerPart.java:413)
at
org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:800)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:871)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$3.run(PackageExplorerContentProvider.java:559)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$7.run(PackageExplorerContentProvider.java:601)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:106)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2702)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2394)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:136)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:261)
at
org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:397)
at
org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:238)
at org.eclipse.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:428)
at
org.eclipse.jdt.internal.ui.refactoring.reorg.DeleteAction.run(DeleteAction.java:88)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:212)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:188)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at org.eclipse.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:212)
at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:141)
at org.eclipse.ui.internal.commands.Command.execute(Command.java:132)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:886)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:927)
at
org.eclipse.ui.internal.keys.OutOfOrderListener.handleEvent(OutOfOrderListener.java:67)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:820)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:805)
at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:1724)
at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:1720)
at org.eclipse.swt.widgets.Control.WM_KEYDOWN(Control.java:3499)
at org.eclipse.swt.widgets.Tree.WM_KEYDOWN(Tree.java:1378)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:2978)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3291)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1466)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2388)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1353)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1324)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:243)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:298)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:249)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:269)
at org.eclipse.core.launcher.Main.run(Main.java:722)
at org.eclipse.core.launcher.Main.main(Main.java:706) | normal | RESOLVED | FIXED |
{'$oid': '52e9c14d54dc1c25ebdc0d2c'} | 62,149 | I200405131200
If I switch the perspective bar to be docked under the main toolbar, all of the
buttons are cut off and only a few pixels of their tops are visible under the
main toolbar. If I shut down eclipse and restart it, the perspective bar is
shown at its full height. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c14d54dc1c25ebdc0d2d'} | 62,157 | Suppose the following queries have been saved:
1. A query with "entire concern model" scope, such as the RegisterCalls query
from the demo.
2. A query with "other concerns" scope, such as the ConmanOperators query from
the demo.
Select saved query 2 - the "other concerns" button is set, correctly.
Then select saved query 1 - both radio buttons appear set.
(I think this is just a display refresh issue, and that the internal variable
behind the radio buttons is correct, but I have not checked carefully). | normal | RESOLVED | FIXED |
{'$oid': '52e9c14d54dc1c25ebdc0d2e'} | 62,158 | j2sdk1.4.2_03 installed, j2sdk1.4.2_03\bin in system path, first launch fails:
!SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 May 13, 2004 14:32:54.505
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.NoSuchMethodError
at
org.eclipse.osgi.framework.util.SecureAction.getFileOutputStream(SecureAction.java:102)
at
org.eclipse.osgi.framework.internal.defaultadaptor.DefaultLog.openFile(DefaultLog.java:106)
at
org.eclipse.osgi.framework.internal.defaultadaptor.DefaultLog.log(DefaultLog.java:146)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:125)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676) | major | CLOSED | DUPLICATE |
{'$oid': '52e9c14d54dc1c25ebdc0d2f'} | 62,159 | 20040511-1600
If I have two perspectives open and a close one the chevron does not go away
even if I don't need it.
STEPS
1) Open Resource and CVS perspectives.
2) Close the CVS perspective
3) Chevron remains | normal | RESOLVED | FIXED |
{'$oid': '52e9c14d54dc1c25ebdc0d30'} | 62,161 | The import plug-ins wizard stays modal after clicking finish.
The operation takes some time and it would benefit it it could be done as a
background operation. | enhancement | RESOLVED | DUPLICATE |
{'$oid': '52e9c14d54dc1c25ebdc0d31'} | 62,160 | If I enter more than one log in the log import wizard, only the first log will
show data and all the other ones are empty. | major | CLOSED | FIXED |
{'$oid': '52e9c14d54dc1c25ebdc0d32'} | 62,162 | major | RESOLVED | FIXED |
|
{'$oid': '52e9c14d54dc1c25ebdc0d33'} | 62,163 | This is a request to have the progress of the background compilation show which
project is currently being compiled. From the M8 'new and noteworthy features'
documentation it looks like a background compilation will show:
Building Workspace: (33%)
and this request is for it to show a bit more information in both the status bar
and hover pop-up, something like:
Building Workspace: (33%) Project 52 of 158
- Currently compiling MyJavaProject (only in the hover pop-up)
This way the end-user knows which project is currently being compiled and how
many are left to go. So if they wish to leave their desk while the compilation
finishes then they will know roughly how long to wait, especially if they have a
large amount of projects in their workspace. | enhancement | RESOLVED | WONTFIX |
{'$oid': '52e9c14d54dc1c25ebdc0d34'} | 62,164 | The goal is to see:
1.) Are we using significantly more memory than prior versions (discounting
memory leaks)?
2.) If so, are there any ways to reduce this memory consumption?
My methodolgy for the first phase is to do the following. Start with a fresh
workspace, switch to the CVS perspective. Check out the platform-ui module.
Switch to the Java perspective. Replace each project with the tagged version
matching the running version. Import all other plug-ins as binary. Open ten
editors. Activate my memory consumption action set, and check the memory after
garbage collection. | normal | VERIFIED | WORKSFORME |
{'$oid': '52e9c14e54dc1c25ebdc0d35'} | 62,165 | I200405131200
To reproduce:
1. Have two editors open
2. Have focus in a view
3. Close one of the editors without switching focus to it (use the X button)
4. Observe that focus now switches to the other editor
This is a regression, in 2.1.3 focus stays in the view you are in. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d36'} | 62,166 | Right click on an agent -> properties -> next -> next. This page is for
debugging purposes and shows the collection mode and RAC options sent for this
agent. There are duplicates in the list of options; should investigate why this
is so. | minor | CLOSED | DUPLICATE |
{'$oid': '52e9c14e54dc1c25ebdc0d37'} | 62,167 | In the launch config dialog where you specify a runtime workbench, you can
specify your own workspace data location. By accident I recently set this
location to the location of the currently running (host) workspace location.
Since I also had "clear" contents checked, my entire workspace was erased
including a bunch of changes I made but didn't commit to CVS.
The wizard should flag an error in this case, since it doesn't make much sense
to have the runtime workspace location the same as the location of the currently
running eclipse. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c14e54dc1c25ebdc0d38'} | 62,168 | With 3.0 M8:
Create a new class (.java file).
Select the file in Package Explorer.
Hit delete key.
Click "Yes" to confirm deletion.
Error box pops up:
"An exception has been caught while processing the refactoring 'Delete'.
Reason:
Exception does not provide a detail message
Click "Undo" to undo all successfully executed changes.
Click "Abort" to abort the refactoring."
The same error box pops up if I try to do a "Move" refactoring (with 'Move' in
place of 'Delete'). | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c14e54dc1c25ebdc0d39'} | 62,169 | selecting a closed project will cause an error later in recording. | minor | CLOSED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d3a'} | 62,170 | In the I0513 build
- Close all of the views in the resource perspective
- Exit
- restar with core.runtime debugging turned on
The following plugins are activated:
Install location:
file:/c:/0513/eclipse/
Configuration file:
file:/c:/0513/eclipse/configuration/config.ini loaded
Configuration location:
file:/c:/0513/eclipse/configuration/
Configuration file:
file:/c:/0513/eclipse/configuration/config.ini loaded
Framework located:
file:/c:/0513/eclipse/plugins/org.eclipse.osgi_3.0.0/
Loading framework classpath from:
file:/c:/0513/eclipse/plugins/org.eclipse.osgi_3.0.0/eclipse.properties
Framework classpath:
file:/c:/0513/eclipse/plugins/org.eclipse.osgi_3.0.0/core.jar
file:/c:/0513/eclipse/plugins/org.eclipse.osgi_3.0.0/console.jar
file:/c:/0513/eclipse/plugins/org.eclipse.osgi_3.0.0/osgi.jar
file:/c:/0513/eclipse/plugins/org.eclipse.osgi_3.0.0/resolver.jar
file:/c:/0513/eclipse/plugins/org.eclipse.osgi_3.0.0/defaultAdaptor.jar
file:/c:/0513/eclipse/plugins/org.eclipse.osgi_3.0.0/eclipseAdaptor.jar
Splash location:
c:\0513\eclipse\plugins\org.eclipse.platform_3.0.0\splash.bmp
Debug options:
file:/C:/0513/eclipse/.options loaded
Starting org.eclipse.core.runtime
End starting org.eclipse.core.runtime 0
Starting org.eclipse.update.configurator
End starting org.eclipse.update.configurator 0
Time to load bundles: 16
Reading registry cache: 78
Starting org.eclipse.ui.ide
Starting org.eclipse.ui.workbench
Starting org.eclipse.jface
End starting org.eclipse.jface 0
Starting org.eclipse.ui
End starting org.eclipse.ui 16
End starting org.eclipse.ui.workbench 63
End starting org.eclipse.ui.ide 78
Starting org.eclipse.core.resources
End starting org.eclipse.core.resources 750
Starting org.eclipse.help
End starting org.eclipse.help 0
Starting org.eclipse.ui.externaltools
End starting org.eclipse.ui.externaltools 0
Starting org.eclipse.debug.ui
Starting org.eclipse.debug.core
End starting org.eclipse.debug.core 0
End starting org.eclipse.debug.ui 31
Starting org.eclipse.core.expressions
End starting org.eclipse.core.expressions 0
Starting org.eclipse.ui.cheatsheets
End starting org.eclipse.ui.cheatsheets 0
Startup complete: 3844ms
Starting org.eclipse.update.scheduler
End starting org.eclipse.update.scheduler 16
These plugins should not have been started:
Starting org.eclipse.help
Starting org.eclipse.ui.externaltools
Starting org.eclipse.debug.ui
Starting org.eclipse.debug.core
Starting org.eclipse.core.expressions
Starting org.eclipse.ui.cheatsheets
If you then open the navigator the following plugins are activated:
Starting org.eclipse.ui.views
End starting org.eclipse.ui.views 0
Starting org.eclipse.team.cvs.ui
Starting org.eclipse.team.core
End starting org.eclipse.team.core 16
Starting org.eclipse.team.cvs.core
End starting org.eclipse.team.cvs.core 110
Starting org.eclipse.team.ui
Starting org.eclipse.compare
End starting org.eclipse.compare 78
End starting org.eclipse.team.ui 141
Starting org.eclipse.ui.console
Starting org.eclipse.text
End starting org.eclipse.text 0
Starting org.eclipse.jface.text
End starting org.eclipse.ui.console 0
End starting org.eclipse.jface.text 0
End starting org.eclipse.team.cvs.ui 516
I can understand activating the "views" plugin. All of the other ones should
not have been activated. | critical | RESOLVED | WONTFIX |
{'$oid': '52e9c14e54dc1c25ebdc0d3b'} | 62,172 | Regression:
Entering !@#$%.rec as filename will give warning but still allow to progress. | minor | CLOSED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d3c'} | 62,174 | After instrumenting core.runtime in M8, I get these numbers:
Eclipse 3.0M8
.registry size = 550 KB
Reading registry took 281 millis
registry needs 1296032 bytes
reading it needs 40596 temporary bytes
WSAD 6.0 on 3.0M8
.registry size = 2.4 MB
Reading registry took 1122 millis
registry needs 5320840 bytes
reading it needs 922032 temporary bytes
Now, 270-280 ms for Eclipse startup is probably just fine.
Over one second for WSAD is definitely an issue.
I noticed the frequent calls to DataInputStream.readUTF() and the occurrence of
repetitive Strings. You should perhaps use a dictionary at the start of the
registry? The trick is to avoid creating many temporary strings which are
then directly discarded due to the call to java.lang.String.intern().
Have you considered using good-old Java serialization? | normal | RESOLVED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d3d'} | 62,173 | I'm using M8. I have seen this once before with M8, but never with any
previous version (I used M7, M6, and M5 quite a bit). One other developer I
know has seen the same problem.
The problem is that somehow eclipse gets into a mode where it doesn't
correctly position the cursor after I select a completion proposal. The
cursor is placed too many characters beyond where it's supposed to be (as it
happens, the extra distance is the same number of characters that were added
by the completion operation). Although you will probably not be able to
reproduce this, I am submitting it in the hope that you can look at the code
and see what could possibly be causing it.
So, if I have the following snippet:
get().getDocument(getEditorInput()).getLineOfOffset(100);
I put the cursor after "get" and hit ctrl+space. I scroll down to
the "getDocumentProvider" item and hit return. The string is completed
correctly, but the cursor ends up after the "g" in "getEditorInput".
If I type in "getDocumentProvide" and hit ctrl+space after the "e", then the
last character is added, but the cursor is placed after the "(".
Once the problem manifests, it is consistent.
Workaround: closing and reopening the affected source editor seems to fix the
problem. | normal | RESOLVED | INVALID |
{'$oid': '52e9c14e54dc1c25ebdc0d3e'} | 62,175 | 1) Open build editor or switch to build page in the manifest editor
2) Check something in either bin or source trees
3) Revert
Observe: the item does not get unchecked | normal | VERIFIED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d3f'} | 62,176 | 20040513 8AM
Starting my test workspace, I noticed a repeatable build on startup. The delta
for each project has 1 delta.
The new ProjectInfo has a single change... its description field is set & was
null in the old ProjectInfo. | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c14e54dc1c25ebdc0d40'} | 62,177 | i200405130010
This is probably known, but... for new-style plug-in manifests (like
core.runtime's), that do not contain a plug-in identifier, searching for
references to any of its extension points fails to find any results. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d41'} | 62,178 | EMF CBE XML SAX parser does not handle XML anyElements (e.g. CBE's otherData).
The EventFormatter JUnit test suite contains two failing test cases due to this
defect.
The EMF CBE XML SAX parser throws SAXParserException when attempting to parse
the following CBE XML document:
<?xml version="1.0" encoding="UTF-8"?>
<CommonBaseEvents xmlns=" http://www.ibm.com/AC/commonbaseevent1_0_1";
xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation=" http://www.ibm.com/AC/commonbaseevent1_0_1
commonbaseevent1_0_1.xsd ">
<CommonBaseEvent creationTime="2001-12-31T12:00:00" elapsedTime="0"
extensionName="Name"
globalInstanceId="i0000000000000000000000000000040" localInstanceId="" msg=""
priority="0" repeatCount="0"
sequenceNumber="0" severity="0" version="">
<contextDataElements name="myContext" type="String">
<contextValue>contextValue</contextValue>
</contextDataElements>
<extendedDataElements name="" type="noValue">
<values>values</values>
<children name="" type="noValue">
<values>values</values>
</children>
</extendedDataElements>
<associatedEvents resolvedEvents="i0000000000000000000000000000040">
<associationEngineInfo id="i0000000000000000000000000000044"
name="MyCorrelationEngine" type="Correlate"/>
</associatedEvents>
<reporterComponentId application="" componentType="" component=""
componentIdType="" executionEnvironment=""
instanceId="" location="" locationType="Name" processId="" subComponent=""
threadId=""/>
<sourceComponentId application="" componentType="" component=""
componentIdType="" executionEnvironment=""
instanceId="" location="" locationType="Name" processId="" subComponent=""
threadId=""/>
<msgDataElement msgLocale="EN">
<msgCatalogTokens value=""/>
<msgId>msgId</msgId>
<msgIdType>Name</msgIdType>
<msgCatalogId>msgCatalogId</msgCatalogId>
<msgCatalogType>msgCatalogType</msgCatalogType>
<msgCatalog>msgCatalog</msgCatalog>
</msgDataElement>
<situation categoryName="StartSituation">
<situationType reasoningScope="EXTERNAL" successDisposition="SUCCESSFUL"
situationQualifier="START
COMPLETED" xsi:type="StartSituation" />
</situation>
<a:a xmlns:a=" http://bar"; />
</CommonBaseEvent>
</CommonBaseEvents> | normal | CLOSED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d42'} | 62,179 | Now that we have mutliple components initialized the same method, selecting on a
component should drive one to the init expression (if there is one), vs. the method. | major | CLOSED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d43'} | 62,171 | When I start WSAD into its J2EE perspective, a draw2d.Figure is used.
When I measure startup performance, getTextForSpace uses 5% of all CPU
needed, allocates 1% of all objects, and makes 7% of all calls. Again,
this if for --complete-- startup of WSAD.
The reason is the use of java.text.BreakIterator. Its first use results
in 6 classes being loaded, and it makes more than a million calls.
All successive calls are much less expensive.
I strongly recommend avoiding BreakIterator and use a different strategy
for determining when to wrap a line. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c14e54dc1c25ebdc0d44'} | 62,181 | Need a getProperties() method in the EDataObject class that retrieves
both static (those defined in the EClass) and dynamic (those defined using
FeatureMaps)
Properties. | normal | VERIFIED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d45'} | 62,180 | I200405111200
To recreate, resize the CBanner such that there is room for all the items.
Notice that the chevron never disappears. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c14e54dc1c25ebdc0d46'} | 62,182 | i200405130010
Organize imports does not work for me with this build:
!ENTRY org.eclipse.ui 4 4 May 13, 2004 16:46:45.990
!MESSAGE The command for the key you pressed failed
!ENTRY org.eclipse.ui 4 0 May 13, 2004 16:46:45.990
!MESSAGE The command for the key you pressed failed
!STACK 0
java.lang.NullPointerException
at
org.eclipse.jdt.internal.ui.util.ElementValidator.getResources(ElementValidator.java:203)
at
org.eclipse.jdt.internal.ui.util.ElementValidator.check(ElementValidator.java:163)
at
org.eclipse.jdt.internal.ui.util.ElementValidator.check(ElementValidator.java:140)
at
org.eclipse.jdt.ui.actions.OrganizeImportsAction.run(OrganizeImportsAction.java:406)
at
org.eclipse.jdt.ui.actions.OrganizeImportsAction.run(OrganizeImportsAction.java:268)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:216)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:188)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:141)
at org.eclipse.ui.internal.commands.Command.execute(Command.java:132)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:886)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:927)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:545)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$2(WorkbenchKeyboard.java:493)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard$1.handleEvent(WorkbenchKeyboard.java:258)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:712)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:795)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:820)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:805)
at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:1724)
at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:1720)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3048)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:2951)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3291)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1466)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2388)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1353)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1324)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:243)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:298)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:249)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:269)
at org.eclipse.core.launcher.Main.run(Main.java:722)
at org.eclipse.core.launcher.Main.main(Main.java:706) | normal | RESOLVED | FIXED |
{'$oid': '52e9c14e54dc1c25ebdc0d48'} | 62,184 | Hi,
I recently downloaded Eclipse 3.0M8 and CDT 2.0M8. In the C/C++ Perspective
if I do a new Project I don't see the C++ Project option at all.
Thanks
Magesh. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d49'} | 62,185 | Build id: 200405131200, and earlier ones.
If you choose a workspace that is in use, an error message appears, but you can
no longer choose a new workspace - even those that are not in use. You must
cancel and try again.
Steps:
1. Open Eclipse with Workspace A.
2. Open Eclipse, choose Workspace A. (Obviously in use)
3. Try to choose Workspace B, or create a new workspace - (which will create the
folder, but still doesn't work) | normal | RESOLVED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d4a'} | 62,186 | After running a URL test that successfully generates an execution history,
reports cannot be generated. | normal | CLOSED | DUPLICATE |
{'$oid': '52e9c14f54dc1c25ebdc0d4b'} | 62,187 | The eInverseRemove needs to clear the container properly. | normal | VERIFIED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d4c'} | 62,188 | I often find myself trying to use the mouse wheel to scroll up and down a
sequence diagram, only to find that it doesn't work. This is quite instinctive
behavior for people who can't live without scroll wheels on their mice. I think
it would be beneficial to have this. | normal | CLOSED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d4d'} | 62,189 | If the runner fails to start a Hyades test (for one of a number of reasons --
unable to load the test class, for example), the model loader is rejecting the
error event, and the user is not informed that the test run failed. | normal | CLOSED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d4e'} | 62,190 | Build 200405131200
I found the following in my .log file. I believe this happened when I closed a bunch of editors
(including PDE editors) which hadn't been reinstantiated yet.
java.lang.NullPointerException
at org.eclipse.ui.forms.editor.FormEditor.dispose(FormEditor.java:236)
at org.eclipse.pde.internal.ui.editor.PDEFormEditor.dispose(PDEFormEditor.java:331)
at org.eclipse.ui.internal.WorkbenchPartReference.dispose(WorkbenchPartReference.java:162)
at org.eclipse.ui.internal.EditorManager$Editor.dispose(EditorManager.java:1195)
at org.eclipse.ui.internal.WorkbenchPage$5.run(WorkbenchPage.java:1150)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:607)
at org.eclipse.core.runtime.Platform.run(Platform.java:668)
at org.eclipse.ui.internal.WorkbenchPage.disposePart(WorkbenchPage.java:1148)
at org.eclipse.ui.internal.WorkbenchPage.closeEditor(WorkbenchPage.java:948)
at org.eclipse.ui.views.editorlist.EditorList.closeSelectedEditors(EditorList.java:208)
at org.eclipse.ui.views.editorlist.EditorListListener.keyReleased(EditorListListener.java:142)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:127)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:939)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:963)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:948)
at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:2284)
at org.eclipse.swt.widgets.Control.gtk_key_release_event(Control.java:1795)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1190)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3036)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(Native Method)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:839)
at org.eclipse.swt.internal.gtk.OS.gtk_main_iteration(Native Method)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2248)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1353)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1324)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:243)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:298)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:249)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:269)
at org.eclipse.core.launcher.Main.run(Main.java:722)
at org.eclipse.core.launcher.Main.main(Main.java:706) | normal | RESOLVED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d4f'} | 62,191 | A newly-identified restriction on Probekit source files should be documented.
The restriction is that they have to appear in a directory that the JDT
identifies as a "source" directory. They can't appear in a subdirectory of such
a directory - if they do, the generated Java source files won't compile.
Users have already run into this and I want to get it in the docs as a
usability improvement. | normal | CLOSED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d50'} | 62,192 | I have a workspace which does not contains any projects loaded from the
repository. I started up in the resource perspective but without any views open,
Then I opened the navigator and which triggered decoratoraction, causing the
team.ui and team.cvs.ui plugins to be activated.
In this scenario they respectively caused the activation of org.eclipse.compare,
and org.eclipse.team.core, org.eclipse.team.cvs.core, org.eclipse.ui.console,
org.eclipse.text. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d51'} | 62,193 | Build 200405131200
Summary says it all. The "Run To Line" action no longer appears in the context menu, where it's
most needed. | major | VERIFIED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d52'} | 62,194 | On a regular eclipse startup, resource perspective, no resources in the
workspace, I can see that the debug UI and that the cheatsheets are activated.
Using the core tools, I found that it is due to the
WorkbenchWindow#updateActionBars().
I included generated stack trace for the activation of those two plugins.
Activating plugin: org.eclipse.ui.cheatsheets
Plugin activation stack:
org.eclipse.ui.cheatsheets
Class loading stack:
Stack trace:
java.lang.Throwable
at java.lang.Throwable.<init>(Throwable.java)
at org.eclipse.osgi.framework.stats.StatsManager.traceActivate(StatsManager.java)
at
org.eclipse.osgi.framework.stats.StatsManager.startActivation(StatsManager.java:125)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:394)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:298)
at
org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java)
at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java)
at java.lang.ClassLoader.loadClass(ClassLoader.java)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:304)
at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:336)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1315)
at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:131)
at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:124)
at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:113)
at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:186)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at
org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:183)
at org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:114)
at
org.eclipse.ui.internal.WWinPluginPulldown.getPulldownDelegate(WWinPluginPulldown.java:197)
at
org.eclipse.ui.internal.WWinPluginPulldown$MenuProxy.getMenu(WWinPluginPulldown.java:148)
at
org.eclipse.jface.action.ActionContributionItem.fill(ActionContributionItem.java:611)
at org.eclipse.jface.action.SubContributionItem.fill(SubContributionItem.java:58)
at org.eclipse.jface.action.MenuManager.update(MenuManager.java:603)
at org.eclipse.jface.action.MenuManager.updateAll(MenuManager.java:697)
at org.eclipse.jface.action.MenuManager.update(MenuManager.java:622)
at org.eclipse.jface.action.MenuManager.updateAll(MenuManager.java:697)
at
org.eclipse.ui.internal.WorkbenchWindow.updateActionBars(WorkbenchWindow.java:2092)
at
org.eclipse.ui.internal.WorkbenchWindow.updateActionSets(WorkbenchWindow.java:2114)
at org.eclipse.ui.internal.WorkbenchWindow$7.run(WorkbenchWindow.java:1922)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:1897)
at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1465)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1206)
at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1173)
at org.eclipse.ui.internal.Workbench$13.run(Workbench.java:1084)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:607)
at org.eclipse.core.runtime.Platform.run(Platform.java:668)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1017)
at
org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:167)
at
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:648)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:807)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1301)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:243)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:298)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:249)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:59)
at java.lang.reflect.Method.invoke(Method.java:389)
at org.eclipse.core.launcher.Main.basicRun(Main.java:269)
at org.eclipse.core.launcher.Main.run(Main.java:722)
at org.eclipse.core.launcher.Main.main(Main.java:706)
Activating plugin: org.eclipse.ui.cheatsheets
Plugin activation stack:
org.eclipse.ui.cheatsheets
Class loading stack:
Stack trace:
java.lang.Throwable
at java.lang.Throwable.<init>(Throwable.java)
at org.eclipse.osgi.framework.stats.StatsManager.traceActivate(StatsManager.java)
at
org.eclipse.osgi.framework.stats.StatsManager.startActivation(StatsManager.java:125)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:394)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:298)
at
org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java)
at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java)
at java.lang.ClassLoader.loadClass(ClassLoader.java)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:304)
at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:336)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1315)
at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:131)
at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:124)
at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:113)
at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:186)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at
org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:183)
at org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:114)
at
org.eclipse.ui.internal.WWinPluginPulldown.getPulldownDelegate(WWinPluginPulldown.java:197)
at
org.eclipse.ui.internal.WWinPluginPulldown$MenuProxy.getMenu(WWinPluginPulldown.java:148)
at
org.eclipse.jface.action.ActionContributionItem.fill(ActionContributionItem.java:611)
at org.eclipse.jface.action.SubContributionItem.fill(SubContributionItem.java:58)
at org.eclipse.jface.action.MenuManager.update(MenuManager.java:603)
at org.eclipse.jface.action.MenuManager.updateAll(MenuManager.java:697)
at org.eclipse.jface.action.MenuManager.update(MenuManager.java:622)
at org.eclipse.jface.action.MenuManager.updateAll(MenuManager.java:697)
at
org.eclipse.ui.internal.WorkbenchWindow.updateActionBars(WorkbenchWindow.java:2092)
at
org.eclipse.ui.internal.WorkbenchWindow.updateActionSets(WorkbenchWindow.java:2114)
at org.eclipse.ui.internal.WorkbenchWindow$7.run(WorkbenchWindow.java:1922)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:1897)
at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1465)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1206)
at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1173)
at org.eclipse.ui.internal.Workbench$13.run(Workbench.java:1084)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:607)
at org.eclipse.core.runtime.Platform.run(Platform.java:668)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1017)
at
org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:167)
at
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:648)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:807)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1301)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:243)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:298)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:249)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:59)
at java.lang.reflect.Method.invoke(Method.java:389)
at org.eclipse.core.launcher.Main.basicRun(Main.java:269)
at org.eclipse.core.launcher.Main.run(Main.java:722)
at org.eclipse.core.launcher.Main.main(Main.java:706) | major | RESOLVED | DUPLICATE |
{'$oid': '52e9c14f54dc1c25ebdc0d53'} | 62,195 | I200405131200
In the JavaDoc of SWT#SCROLL_LOCK the 'num' should be replaced by 'scroll'. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d54'} | 62,196 | In Window->Preference->Run/Debug->Launching,
'Remove terminated launches when a new launch is created' is checked by default
which introduce usability problem to profiling and logging feature as the
launches are used to link with console output/input of any application
profiled. Removing lauches after terminated means console output will be gone
once the application profiled is termainted.
Is there any reason why it is set to default? | enhancement | CLOSED | WONTFIX |
{'$oid': '52e9c14f54dc1c25ebdc0d55'} | 62,197 | Whenever I close Eclipse, and reopen it, some plugin projects show up with
compilation errors. These errors are always related to plugin dependencies. I
have to open the plugin.xml file, make a change (adding a space in the source
view for example) and then save the file. The project becomes error-free. I
must do this for each project that contains errors.
I know this is vague. My IDE contains over 8 plugin projects. This error is
always hapenning. | normal | RESOLVED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d56'} | 62,198 | The current Probekit instrumentation implementation throws an exception if you
feed it files that have already been instrumented. This used to be a
requirement, back when all generated probe classes had the same name. But now
they have different names, and you can instrument the same class file multiple
times without problems.
This can prove serious: one use case for probes is that a developer can
incorporate them as part of a deployed project, and then the customer might
want to apply another set of probes in the field - we shouldn't deny this.
Sadly, this limits the static instrumenter's ability to report a common user
error, running it on already-instrumented class files when the intention was to
run it on the original class files. | major | CLOSED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d57'} | 62,199 | Here is the aspect:
package com.sampullara.testing;
public aspect UsedClasses {
pointcut scope() : staticinitialization(*) && !within(com.sampullara.testing.UsedClasses);
before() : scope() {
System.out.println("[Initializing class: " + thisJoinPointStaticPart.getSourceLocation() + "]");
}
}
/Users/sam/Software/WLS-STAGE/wls/server/lib:> time ajc -injars weblogic.jar -outjar
newweblogic.jar -sourceroots ~/Projects/AspectJ/UsedClasses/src
ABORT
Exception thrown from AspectJ 1.2rc1
This might be logged as a bug already -- find current bugs at
http://bugs.eclipse.org/bugs/buglist.cgi?product=AspectJ&component=Compiler
Bugs for exceptions thrown have titles File:line from the top stack,
e.g., "SomeFile.java:243"
If you don't find the exception below in a bug, please add a new bug
at http://bugs.eclipse.org/bugs/enter_bug.cgi?product=AspectJ
To make the bug a priority, please include a test program
that can reproduce this exception.
null
java.lang.NullPointerException
at org.eclipse.jdt.internal.compiler.CompilationResult.computePriority(CompilationResult.java:110)
at org.eclipse.jdt.internal.compiler.CompilationResult.quickPrioritize(CompilationResult.java:336)
at org.eclipse.jdt.internal.compiler.CompilationResult.getProblems(CompilationResult.java:230)
at org.eclipse.jdt.internal.compiler.CompilationResult.getAllProblems(CompilationResult.java:118)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager$4.acceptResult(AjBuildManager.java:661)
at org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.acceptResult(AjCompilerAdapter.java:178)
at org.aspectj.ajdt.internal.compiler.WeaverAdapter.finishedWith(WeaverAdapter.java:203)
at org.aspectj.ajdt.internal.compiler.WeaverAdapter.weaveCompleted(WeaverAdapter.java:167)
at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:570)
at org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.weave(AjCompilerAdapter.java:239)
at org.aspectj.ajdt.internal.compiler.AjCompilerAdapter.afterCompiling(AjCompilerAdapter.java:
114)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:376)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation(AjBuildManager.java:
600)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:160)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.batchBuild(AjBuildManager.java:94)
at org.aspectj.ajdt.ajc.AjdtCommand.doCommand(AjdtCommand.java:102)
at org.aspectj.ajdt.ajc.AjdtCommand.runCommand(AjdtCommand.java:53)
at org.aspectj.tools.ajc.Main.run(Main.java:280)
at org.aspectj.tools.ajc.Main.runMain(Main.java:217)
at org.aspectj.tools.ajc.Main.main(Main.java:79)
1 fail|abort
real 37m7.541s
user 7m0.690s
sys 0m23.010s | critical | RESOLVED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d58'} | 62,200 | When Bug 60039 is fixed, DisplayView#partHidden(...) should only save its state when the view is
closed for the last time. The code to do this is already in the file; it's just commented out. | normal | VERIFIED | FIXED |
{'$oid': '52e9c14f54dc1c25ebdc0d59'} | 62,201 | I200404131200 + jdt.debug.ui from HEAD
You need jdt.debug.ui from HEAD, otherwise the completion is not run on the
correct type, you need org.eclipse.text or a plug-in that requires
org.eclipse.text in your workspace.
1. open the detail formatters preference page (prefs>Java>Debug>Detail Formatters)
2. 'add...'
3. type 'org.eclipse.jface.text.IDocument' as name
4. give the focus to the text area
5. hit [Ctrl+Space]
The following stack trace is added to the log
!ENTRY org.eclipse.ui 4 4 May 13, 2004 16:22:41.631
!MESSAGE Unhandled event loop exception
!ENTRY org.eclipse.ui 4 0 May 13, 2004 16:22:41.632
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at java.lang.Throwable.<init>(Throwable.java)
at java.lang.Throwable.<init>(Throwable.java)
at java.lang.NullPointerException.<init>(NullPointerException.java:60)
at
org.eclipse.jdt.internal.compiler.lookup.MethodScope.createMethod(MethodScope.java:299)
at
org.eclipse.jdt.internal.compiler.lookup.ClassScope.buildMethods(ClassScope.java:221)
at
org.eclipse.jdt.internal.compiler.lookup.ClassScope.buildFieldsAndMethods(ClassScope.java:124)
at
org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.buildFieldsAndMethods(CompilationUnitScope.java:61)
at
org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.completeTypeBindings(LookupEnvironment.java:227)
at
org.eclipse.jdt.internal.codeassist.CompletionEngine.complete(CompletionEngine.java:813)
at org.eclipse.jdt.internal.core.BinaryType.codeComplete(BinaryType.java:91)
at org.eclipse.jdt.internal.core.BinaryType.codeComplete(BinaryType.java:58)
at
org.eclipse.jdt.internal.debug.ui.DetailFormatterCompletionProcessor.computeCompletionProposals(DetailFormatterCompletionProcessor.java:50)
at
org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1457)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:244)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$7(CompletionProposalPopup.java:240)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup$1.run(CompletionProposalPopup.java:199)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:194)
at
org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1308)
at
org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:683)
at
org.eclipse.jdt.internal.debug.ui.DetailFormatterDialog$1.execute(DetailFormatterDialog.java:150)
at org.eclipse.ui.internal.commands.Command.execute(Command.java:132)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:886)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:927)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:545)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$2(WorkbenchKeyboard.java:493)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard$1.handleEvent(WorkbenchKeyboard.java:258)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:948)
at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:2284)
at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:1784)
at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:441)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java)
at org.eclipse.swt.widgets.Display.windowProc(Display.java)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(Native Method)
at org.eclipse.swt.widgets.Display.eventProc(Display.java)
at org.eclipse.swt.internal.gtk.OS.gtk_main_iteration(Native Method)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:668)
at org.eclipse.jface.window.Window.open(Window.java:648)
at
org.eclipse.jdt.internal.debug.ui.JavaDetailFormattersPreferencePage.addType(JavaDetailFormattersPreferencePage.java:262)
at
org.eclipse.jdt.internal.debug.ui.JavaDetailFormattersPreferencePage$6.handleEvent(JavaDetailFormattersPreferencePage.java:193)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:668)
at org.eclipse.jface.window.Window.open(Window.java:648)
at
org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:72)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:899)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:850)
at
org.eclipse.jface.action.ActionContributionItem$7.handleEvent(ActionContributionItem.java:769)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:939)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1353)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1324)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:243)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:298)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:249)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at org.eclipse.core.launcher.Main.basicRun(Main.java:269)
at org.eclipse.core.launcher.Main.run(Main.java:722)
at org.eclipse.core.launcher.Main.main(Main.java:706) | normal | VERIFIED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d5a'} | 62,203 | Cursor in the left bar for text editors has been recently changed into hand
cursor. I think that this is not the correct cursor in this context. Users are
comfortable with the hyperlink metaphor from the browser world and they expect
single-click action. However, most of the actions require double-click (adding
a breakpoint, setting a bookmark etc.). | normal | RESOLVED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d5b'} | 62,204 | OS X 10.3, but I think its been like this since installation.
I've got an editor window open (several in fact) yet the print command is always disabled.
Why? | major | RESOLVED | WORKSFORME |
{'$oid': '52e9c15054dc1c25ebdc0d5c'} | 62,205 | I report something strange.
Using Eclipse2.1, a Java code like followings don't occured a compile error.
Its code occured an error with Eclipse2.0.
Although it's basically a stupid code, in the world, there is some people who
believe it's OK.
For such a people, I hope it occurs an error.
Perhaps, are there some reason to be like this?
-------------------------
public void foo(){
this = null;
}
------------------------- | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c15054dc1c25ebdc0d5d'} | 62,206 | build I20040513-1200
- my laptop crashed
- on restart of Eclipse, did a Ctrl+B (auto-build is off), and ran it in the bg
- this was a full build due to the crash
- while this was going on, edited and saved a file (ViewFactory.java)
- the save was blocked by the build and the blocked progress dialog came up
- the build job was the first one and was working
- the second job was the save, I guess, but its label was the same as the window
title:
Java - ViewFactory.java - d:\eclipse-new\plugins - Eclipse Platform
Perhaps this is because Save uses the window as its runnable context?
A better label would be "Saving ViewFactory.java". Not sure if this is
achievable though. | normal | VERIFIED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d5e'} | 62,202 | If launcher contributions/shortcuts are mapped to activities they are filtered
out when activity is disabled, however contributions to the Run-> context menu
are all there even related activities are disabled. | normal | VERIFIED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d5f'} | 62,207 | I don't know how I triggered it but I got a fecthing children job for every
project in dev.eclipse.org when I performed a checkout with the toolbar
checkout wizard. I choose an exisiting project from the list but somehow I
also triggered the expansion of every item in the list. We need to add code to
the wizard that will kill any jobs launch from the wizard (as was done in the
repositories view) | critical | RESOLVED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d60'} | 62,208 | I thought I fixed the lazy enablement of the CVS decorator but it turns out I
was fooled because I didn't disable the decorator in XML. When I fixed that,
it surfaced a bug in UI where the programmatic setting of decorators doesn't
take. It appears to work (it is checked on the preference page) but some items
are not decorated (a few are but most are not) and the setting is lost after a
restart. It should be straight forward to duplicate the behavior present in
the preferences dialog (i.e. to make it work properly). I will try it out and
send a patch to UI when completed. | normal | VERIFIED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d61'} | 62,209 | Even read-only cursor movement and scrolling are substantially degraded/ poorly
responsive with a moderate sized block of pasted code in need of refactoring.
This block is 220 lines with 75 errors markers.
Poor responsiveness (5 seconds for scroll wheel activity to be completed) is
probably associated with broken Ctrl-C shortcut in similar situations.
The poor performance indicates major inefficiency in marker display or data
structures. I've noticed in the past that markers (error statuses, breakpoints
etc) seem to be one of the weakest parts of Eclipse.
Cheers,
Thomas | normal | RESOLVED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d62'} | 62,210 | build I20040513-1200
- minimize a view along the bottom of the window
- right click on its tab
- it gets restored on right button down
- the menu still pops up on button up, but the view's titlebar may have been
warped a fair distance away from where the menu pops up
It would be better if right click did not restore. There's a restore item on
the menu if that's what the user wanted, but they should also be able to go
directly to maximize, fast view or close from the minimized state. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c15054dc1c25ebdc0d63'} | 62,211 | Hi, Eclipse 3m8 and previous versions --
1) Conditional Breakpoint has poor ergonomics. Toggle, then Properties, then
Enable Condition, then finally specifying the actual condition.
Recommendation: add 'Condition Break...' to right-click menu. Should create
new/ set condition on existing breakpoint; placing the focus in the 'condition'
box.
2) Conditional Breakpoint is significantly unreliable (jdk 1.4.2_01). Invalid
stack frames, errors compiling etc mean that conditions frequently just don't
work. Could be a JDK version issue I know.
Cheers,
Thomas | enhancement | RESOLVED | WONTFIX |
{'$oid': '52e9c15054dc1c25ebdc0d64'} | 62,213 | Hi people,
Testing & debugging within larger software frequently wants breakpoints to be
active only while executing within a certain problem section of the test.
The proposal is to allow users to create 'Guard Entry' and 'Guard Exit' points.
Arrival at the 'entry' would not stop execution but would enable all 'normal'
breakpoints. Arrival at the 'exit' would disable all normal breakpoints.
The 'Guard Points' would be major switches to which all normal BPs would then
be subservient. (Simplest conceptual use). They would be shown at the top of
the BP list. Check status of BPs switched by the guards would not be changed,
they would just be inapplicable outside guard section.
These would be a majorly productive tool, I think these would be a lot of help
to all of you guys and everyone else working on larger software.
Cheers,
Thomas | enhancement | RESOLVED | DUPLICATE |
{'$oid': '52e9c15054dc1c25ebdc0d65'} | 62,214 | Hi people,
JUnit usage and testing would be a *lot* more convenient if the JUnit panel was
more flexible and interactive.
Selecting a specific test or tests to run, would be much quicker and more
friendly than manually modifying & rebuilding the test classes.
Also an option to halt on failure would be extremely desirable, to allow direct
switchover to the investigate/ fix phase; and additionally so that the console
output logging the failure has not long gone.
Lastly the 'Rerun test' option fails pretty frequently, tries to do something
and then just exits out, would be nice if this was actually somewhat robust.
These measures would be substantial improvements on what is a useful but not
ideally usable tool.
Cheers,
Thomas
PS: Not sure if this is the right category, please reassign if there is a more
appropriate one. | enhancement | CLOSED | WONTFIX |
{'$oid': '52e9c15054dc1c25ebdc0d67'} | 62,212 | build I20040513-1200
- while debugging, I was looking at a stack frame 2 down from the top
- on the line with the highlight, I hovered over the method name of the method
call expression for the next call (the one already shown in the next frame in
the Debug view)
- the hover simply read "Debug Call Stack"
If I hover over other method call expressions, the hover normally shows the
signature of the method and any Javadoc.
While I really like the Debug hover support for showing variable values, I don't
see the benefit in this one. | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c15054dc1c25ebdc0d68'} | 62,216 | (This is actually already in progress; I've added it to Bugzilla solely to be
able to indicate that finishing this feature depends on the resolution of a
new feature enhancement I also just added to Bugzilla. I.e., I'm doing it to
help with tracking, nothing else. :-)) | enhancement | RESOLVED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d69'} | 62,219 | In serviceconfig.xml value of LOCAL_AGENT_TEMP_DIR is defined as %TMP%.
The value of TMP is not set in the serviceconfig.xml file. It is set in the
system environment. So I am guessing the value of LOCAL_AGENT_TEMP_DIR is not
getting set to the value of %TMP% . I debugged the windows code and it looks as
if the value of LOCAL_AGENT_TEMP_DIR is being set to an empty string.
When the method ra_getEnvironmentVariable is called with LOCAL_AGENT_TEMP_DIR
it returns an empty string. Instead of returning the value of %TMP%.
Is this the desired behaviour ? | normal | CLOSED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d6a'} | 62,220 | Eclipse fails to attach to JUnit process when code is located in ClearCase view
(NFS file system). No reproducible if code is placed on a local drive. No
specific messages in .metadata\.log file.
The problem appears to be only in 3.0 branches ( at least on M3,M5,M7, M8; in
2.1.3 everything works Ok.
OS: Windows 2000.
Could not connect to: : 4115
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.connect
(RemoteTestRunner.java:640)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:289)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:182) | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c15054dc1c25ebdc0d6b'} | 62,221 | PreferenceForwarder#contains(String) iterates over the preference keys while
Preferences#contains(String) did a lookup in a hashtable.
This is a performance problem when opening a Java editor and takes ~8% of the
time in I200405130800 with the performance fix from bug 61446 applied.
(I will repeat my measurements with the upcoming I-builds that will include the
above mentioned fix.) | normal | RESOLVED | FIXED |
{'$oid': '52e9c15054dc1c25ebdc0d6c'} | 62,222 | Eclipse 3.0 M8 always asks for the workspace, regardless if only a single
workspace exists or 'Use this as the default and do not ask again.' was checked. | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c15054dc1c25ebdc0d6d'} | 62,217 | This is a regression caused by the patch to bug 62038 | normal | CLOSED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d6e'} | 62,223 | I20040513
1. debugged a run-time workbench.
2. Changed some classes and it was out of synch.
3. Closed the target via its window close handle (X in upper right corner)
-> the target did not shut down
4. In my host workbench, debug view, I hit the terminate button
-> host workbench dead in water, vm thread dump follows | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c15154dc1c25ebdc0d6f'} | 62,224 | Note: This bug report outlines problems similar to, but not described in bug
report 39459, although this report also concerns x-mouse.
Summary
-------
There are several unwanted situations where Eclipse 3.0MS8 in combination with
the tweakui X-Mouse seeting will raise its main window to the top of the z-
order, effectively making all other windows disappear behind it.
Detailed description
--------------------
How to activate "x-mouse":
- download and install Tweakui from Microsoft's Windows XP PowerToys homepage
- start Programs->PowerToys for Windows XP->Tweak UI
- in the new window open section Mouse->X-Mouse
- make selections:
. [X] Activation follows mouse
. [ ] Autoraising when activating
(autoraising not selected!)
Now you have activated the activation style often used on X-Windows (Unix)
systems. It will give the input focus to the window containing the mouse
pointer without having to click the window first. One of the main advantages
is also that you can have the input focus on a window that is not on the top
of the z-order (which is difficult to achieve in standard Windows focus style
as clicking a window will both raise it to top of z-order AND assign input
focus).
Problem 1: Dialog box will raise main window
Reproducing the bug:
- activate X-Mouse as described above
- start Eclipse 3.0MS8 and make it full screen
- open the dialog box Window->Preferences in Eclipse
- start another application, f ex Windows Explorer, and make its window
stay "on top" of the Eclipse window by using Alt-Tab to activate this other
application (Windows will still do a combined activation and raise when using
Alt-Tab).
- now when you move the mouse into Eclipse, its main window will be raised to
top-level (this also happened without open dialogs up to 3.0MS7)
Analysis:
This is probably an old-style way of coding the dialogs that was very common
some years ago on Windows, where you when receiving a SetFocus message always
did a RaiseToTopLevel. For some time a also think this was the standard
behaviour in Microsoft's MFC library but is not anymore.
Anyway, this behaviour is undesired with X-Mouse and today I think this
behaviour also violates Windows design guidelines, in that applications should
not steal focus or popup on top of other applications, but I'm not up-to-date
with the exact phrasing...
Problem 2: Moving mouse into tooltips will raise main window
- activate X-Mouse as described above
- start Eclipse 3.0MS8 and make it full screen
- start another application, f ex Windows Explorer, and make its window
stay "on top" of the Eclipse window by using Alt-Tab to activate this other
application
- move the mouse over the Eclipse toolbar so a tooltip is displayed (Eclipse
main window is still below the other application)
- now quickly move the mouse over the tooltip so you "touch" the tooltip
before it disappears, and the Eclipse main window will be raised to top-level
Analysis:
Probably a similar thing here; when the tooltip window gains focus (caused by
the mouse inside it) it will raise its parent window to top-level.
Problem 3: Mouse inside content assist "documentation" will raise main window
and close content assist
- activate X-Mouse as described above
- start Eclipse 3.0MS8
- find a piece of source code where you can popup content assist with
documentation, for example
String str;
str.
^ do content assist here
- when the content assist displays methods of class String it will also after
a short while display the JavaDoc of the selected method
- start another application, f ex Windows Explorer, and make its window
stay "on top" of the Eclipse window by using Alt-Tab to activate this other
application
- make sure the other application is positioned so it doesn't cover the place
where you want to work with content assist
- position the text cursor back on the end of "str." as before
- move the mouse into the area where you know the JavaDoc will be displayed
- open content assist again, it will open up but will close down as soon it
tries to display the JavaDoc documentation and at the same time raise the main
window
Analysis:
Probably similar coding here; the content assist JavaDoc window will gain
focus when popped up under the mouse, and will then activate its parent
window. It will thereby give away focus from itself and will then decide to
close as this is often the behaviour for these kinds of hover windows. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c15154dc1c25ebdc0d71'} | 62,226 | The filters menu on the search results is currently shown in a submenu. Since
there are only a couple of them we should show the filters inline. Also they
should appear above the layout option. | normal | RESOLVED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d72'} | 62,225 | I200405131600
1. clean all
2. build all
3. open plugin.xml using Plug-in editor
4. change some text
5. save
6. wait.......
Reason: PDE locks the full worksapce instead of using minimal scheduling rule. | normal | RESOLVED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d73'} | 62,228 | The following code snippet inside TableItem throws a NPE. The variable images
is null. I'm using eclipse-SDK-I20040506-win32
if (index != 0 && images != null & images [index] == null) {
width = 0;
} | major | RESOLVED | INVALID |
{'$oid': '52e9c15154dc1c25ebdc0d74'} | 62,227 | The message handler in the weaving adapter for load time weaving says:
public boolean handleMessage(IMessage message) throws AbortException {
if (!isIgnoring(message.getKind())) {
if (verbose) System.err.println(message.getMessage());
throw new AbortException(message);
}
return true;
}
This means for warnings it goes bang. So, even a declare warning that is
meant to tell the user something informational during a LTW will cause the
code to blow up. The fix is straightforward and simply to log warning
messages and only fail for error messages. I am waiting for a testcase from
Matthew before checking in the fix. | major | RESOLVED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d75'} | 62,229 | When selecting a working set as the filter for the problems view then the
problems are sometimes not filtered correctly.
This happens when the working set contains a large number (about 55) of
selected packages.
In this case the result isn't filtered at all. | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c15154dc1c25ebdc0d76'} | 62,230 | I am using 3.0M8 and I have been trying out the comment formatting in the new
code formatter, which I really like.
However we are using SourceSafe and we use the version control to generate a
history in comments in the Java file. Here is an example:
/*
* $History: AllTests.java $
*
* ***************** Version 1 *****************
* User: Fianno Date: 11/03/04 Time: 11:54
* Created in $/Development/Modules/wrttest/src/com/touchclarity/wrttest
*/
This comment is auto generated and preformatted. I need to be able to preserve
the formatting here.
Is it possible to add an option that allows you to activate code formatting
within JavaDoc comments but not inside regular non-JavaDoc comments? At the
moment it seems my only option is to switch off comment formatting completely. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c15154dc1c25ebdc0d77'} | 62,231 | When using an org.eclipse.core.internal.utils.ObjectMap
[I just realised, it's internal so I shouldn't be using it, but anyway]
if the map is empty and entrySet is called then a NullPointerException is
raised in line 243 in the private toHashMap method as 'elements' is
uninitialised.
Soln: Initialise elements in constructor or similar.
BTW when trying to isolate this bug in Eclipse 3.0M3 debugger,
com.sun.jdi.InvocationException was thrown every time I tried to
expand 'this'=ObjectMap. | normal | RESOLVED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d78'} | 62,233 | Found the following NPE in the log.
No reproducable case, sorry.
!SESSION May 13, 2004 23:34:55.865 --------------------------------------------
-
eclipse.buildId=I200405111600
java.version=1.4.2
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -Dosgi.checkConfiguration=true
!ENTRY org.eclipse.core.resources 2 1 May 13, 2004 23:34:55.875
!MESSAGE Skipping builder net.genady.jdk15.Java15Builder for project
ZZZJDK1.5. Either the builder is missing from the install, or it belongs to a
project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 May 13, 2004 23:34:56.255
!MESSAGE Skipping builder org.eclipse.releng.tools.mapFileValidator for
project org.eclipse.releng. Either the builder is missing from the install, or
it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.runtime 4 2 May 14, 2004 09:11:57.609
!MESSAGE An internal error occurred during: "Semantic Highlighting Job".
!STACK 0
java.lang.NullPointerException
at
org.eclipse.jdt.internal.ui.javaeditor.SemanticHighlightingReconciler.reconcile
d(SemanticHighlightingReconciler.java:167)
at
org.eclipse.jdt.internal.ui.javaeditor.SemanticHighlightingReconciler$1.run
(SemanticHighlightingReconciler.java:311)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66) | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c15154dc1c25ebdc0d79'} | 62,234 | Since we cannot move all color settings into Workbench>Colors and Fonts, this
preference page should only be used for Workbench color settings.
This means the Ant color settings should be moved back to the Ant component
node (sorry for this). | normal | VERIFIED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d7a'} | 62,235 | I have several interdependent projects.
For some of them, I have a custom external builders in ant that simply packs the
*.class files in a jar.
One I run the Rebuild all command, I receive the following error:
Build problems
Errors during build.
Ant build E:\DAVID\webIma6.1\copia-areas\build.xml already in progress
It seems a timing problem, when the ant task hasn't been finished, and another
one is tried to execute. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c15154dc1c25ebdc0d7b'} | 62,236 | see bug# 62234 for the explanation | normal | VERIFIED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d7c'} | 62,237 | The syntax coloring settings should provide a preview in the same way as the
Java Editor Java>Editor>Syntax.
Also there should be support to leverage italic | normal | VERIFIED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d7d'} | 62,232 | In I20040506, I have a problem with copy/pasted files.
If I have a Package Explorer view open that shows the contents of a package as:
Aaa
Ccc
Eee
Ggg
And chose to copy/paste one of these classes to make a new one called Bbb,
then all seems to work OK (I get prompted for the new name, the process seems
to complete cleanly, and I can then open Bbb in the Open Type dialog), but the
new class *fails* to appear in the Package Explorer list.
I can also find no way to make the class appear after this has happened
(Refresh etc have no effect). The only thing that works is to shutdown/restart
Eclipse.
Worse than that, if I create Bbb as above, then although the view does not
display the new file, it would appear that its internal state does know about
it. Thus, if I then double-click to open Eee, the class that actually opens is
Ccc...
Eek! | normal | CLOSED | FIXED |
{'$oid': '52e9c15154dc1c25ebdc0d7e'} | 62,238 | The syntax coloring settings should provide a preview in the same way as the
Java Editor Java>Editor>Syntax.
Also there should be support to leverage italic | normal | RESOLVED | DUPLICATE |
Subsets and Splits