_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': '52e9c10d54dc1c25ebdc089e'} | 60,990 | org.eclipse.swt.widgets.Button.selectRadio() method contains the following
commented piece of code that in my opinion should be uncommented to get the
correct behavior. Currently to implement a radio button group a user has to put
it in a separate composite, which may have undesired layout side effects.
void selectRadio () {
/*
* This code is intentionally commented. When two groups
* of radio buttons with the same parent are separated by
* another control, the correct behavior should be that
* the two groups act independently. This is consistent
* with radio tool and menu items. The commented code
* implements this behavior.
*/
// int index = 0;
// Control [] children = parent._getChildren ();
// while (index < children.length && children [index] != this) index++;
// int i = index - 1;
// while (i >= 0 && children [i].setRadioSelection (false)) --i;
// int j = index + 1;
// while (j < children.length && children [j].setRadioSelection (false))
j++;
// setSelection (true);
...
} | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c10d54dc1c25ebdc089f'} | 60,991 | If you spec a UNC path (e.g., \\?\c:\foo) as the workspace location in PDE's
runtime workbench launch configuration dialog the valu is not correctly passed
into the target Eclipse. In the case of the example above, the actual arg that
appears in the target main() is \\foo. The command line for the target has \\?
\c:\foo on it but that may not be the correct incantation. Even if you change
the \ to / you get the same results.
This hinders progress on debugging/resolving bug 60831 | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c10e54dc1c25ebdc08a0'} | 60,992 | build I20040427
- open EditorManager$Editor from source (in org.eclipse.ui.internal)
- Refactor > Move Member Type to New File
- preview is happy
- it extracts OK
- the result has compilation errors due to access to outer private members
The refactoring should generate the necessary accessor methods, in the same
way that the compiler does (although with better names).
(Actually, I almost prefer the fact that it raised these as errors. If I was
forced to fix these up manually, I might not do it the same way as using
accessor methods, but the intent with refactorings is that they preserve
semantics and don't introduce errors.) | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c10e54dc1c25ebdc08a1'} | 60,993 | New feature:- adds the Managed Make nature to any project.
Follow up from bug 60231. | enhancement | RESOLVED | FIXED |
{'$oid': '52e9c10e54dc1c25ebdc08a2'} | 60,994 | in i0504
I'm not sure what user interaction I am expecting but I cannot find a way to
copy a package from one project to another. I am using a perspective that has
a Package Explorer, Package view and types view. If I select the package in
the packages view, Copy and Cut are gray. I can initiate a drag but cannot
find any valid drop zones. I can't even seem to get drag and drop to work for
the classes. In some cases I can Copy but cannot find a place with Paste
enabled.
I don't do this often so am not sure if this is a bug in the build or a truly
missing interaction.
In any event, I have a mess o' packages/classes to copy to another project and
would very much like to avoid the horror of individually creating the classes
with the wizard and then cut and pasting the content! | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c10e54dc1c25ebdc08a3'} | 60,995 | I plan to clean up the Ant use of the deprecated runtime code | normal | VERIFIED | FIXED |
{'$oid': '52e9c10e54dc1c25ebdc08a4'} | 60,997 | The popup menu to select an editor (used when there are many editor windows
open) is hard coded to a background colour of white. This is fine if you use a
typical text colour of black. It's very bad if you use an inverted colour
display scheme, as you end up with pale text on a white background, which is
effectively unreadable (especially on a laptop screen).
The correct behaviour should likely be something along the lines of using the
platforms default tooltip colour, or at least the default text editor background
colour (note, that haven't seen any other popup menus in eclipse with this problem).
The offending code would appear to be in
org.eclipse.ui.internal.presentations.EditorList , in the constructor:
public EditorList(Shell parent, int shellStyle, int treeStyle) {
super(parent, shellStyle, treeStyle);
setBackgroundColor(new Color(parent.getDisplay(), 255, 255, 255));
}
<RANT>I know I don't need to remind you eclipse folks, as you've done a
commendable job so far; for everyone else out there (especially web designers):
if you 'must' hardcode a background colour, you __must__ hard code the
forground colour as well!!!!</RANT>
Thank you :) | normal | CLOSED | FIXED |
{'$oid': '52e9c10e54dc1c25ebdc08a5'} | 60,999 | I started Eclipse, but it closed.A log was generated. | blocker | RESOLVED | DUPLICATE |
{'$oid': '52e9c10e54dc1c25ebdc08a6'} | 61,001 | If I change the FieldName into an aleady existing one, then it would be nice, if
this would be indicated instead of silently refused. Most appreciated way would
be like an indicator when creating a new Class. | minor | CLOSED | WORKSFORME |
{'$oid': '52e9c10e54dc1c25ebdc08a7'} | 60,998 | With eclipse 3.0 When I put the cursor on a class variable and click ctrl+H it
odes not give me the search results. This worked fine wit heclipse 2.0. It
shows zero references. Can you please help me regarding this. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c10e54dc1c25ebdc08a8'} | 61,000 | Hi
I have in my sourcepath two java classes that have the same name and package
name. I know this is stupid, but anyway.....
These two classes are test classes, one is an integration test located in a
"test.integration" source tree, the other a unit test, located in a "test.unit"
tree. They both call and test the same method, let's call the method
WhateverClass.whatEverMethod().
The problem is when I search the workspace for usages of the method
WhateverClass.whatEverMethod(), only one of the two classes using it appears. If
I place the "test.integration" source tree first in the sourcepath, the
integration test pops up as a class that uses WhateverClass.whatEverMethod(). If
I place the "test.unit" source tree first in the sourcepath, the unit test pops
up as a class that uses WhateverClass.whatEverMethod(). But not both at the same
time. This is a bug, isn't it?
Kind Regards
Bård Dybwad Kristensen | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c10e54dc1c25ebdc08a9'} | 61,004 | N20040503 | normal | VERIFIED | FIXED |
{'$oid': '52e9c10e54dc1c25ebdc08aa'} | 61,005 | I20040505-0200
class A {
private void method() {}
}
Show Hierarchy (Ctrl+T) on method()
-> was: classes "Object" and "A", both displayed "disabled"
(white-and-grey icon, grey text)
-> expected: only "Object" is disabled, "A" is colorful (defines the method) | trivial | RESOLVED | FIXED |
{'$oid': '52e9c10e54dc1c25ebdc08ab'} | 61,003 | Then I start Eclipse and switch to Java Perspective the Package Explorer
allways shows contents of the same package, it doesn't store another entry. | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c10e54dc1c25ebdc08ac'} | 61,006 | In the documentation, it is written that it is possible to change the style of
the Text widget to align the text on the right. By default, text is aligned on
the left. So documentation or behaviour is wrong.
Hubert. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c10e54dc1c25ebdc08ad'} | 61,007 | I put my general aspect with an abstract pointcut into one package. The
application-specific (concrete) aspect should be located in another package:
// File aspects/AbstractAspect.java
package aspects;
public abstract aspect AbstractAspect {
abstract pointcut myPointcut();
before(): myPointcut() {
System.out.println("before myPointcut.");
}
}
// File myApp.ConcreteAspect.java
package myApp;
public aspect ConcreteAspect extends aspects.AbstractAspect {
pointcut myPointcut(): execution( void myApp.RunTest.say(String));
}
// File myApp/RunTest.java
package myApp;
public class RunTest{
public static void main(String[] args){
say( "Hello");
}
public static void say(String msg){
System.out.println(msg);
}
}
The ajc-compilers in version 1.1.1 and 1.2rc1 don't compile it:
[jb@SHARK test]$ /usr/local/java/aspectj-1.2rc1/bin/ajc -classpath
.:/usr/local/java/aspectj-1.2rc1/lib/aspectjrt.jar @default.lst
/home/jb/projects/test/aspects/AbstractAspect.java:5 error inherited abstract
pointcut aspects.AbstractAspect.myPointcut() is not made concrete in
myApp.ConcreteAspect
abstract pointcut myPointcut();
^^^^^^^^^^
/home/jb/projects/test/myApp/ConcreteAspect.java:4 error inherited abstract
pointcut aspects.AbstractAspect.myPointcut() is not made concrete in
myApp.ConcreteAspect
public aspect ConcreteAspect extends aspects.AbstractAspect
^^^^^^^^^^^^^
2 errors
If you move ConcreteAspect into the same package as the abstract aspect it works
fine. | normal | RESOLVED | INVALID |
{'$oid': '52e9c10e54dc1c25ebdc08ae'} | 61,002 | When I tell Eclipse to use this command line instead of make, it truncates the
line at the '"'.
c:\cygwin\bin\bash --login -i -c "cd /cygdrive/c/cdtworkspace/colinux-config &&
make"
I'll attach pictures. | enhancement | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08b0'} | 61,010 | Using build I200405050200, I got following exception while trying to open
org.eclipse.jdt.core.tests.compiler/plugin.xml file:
!MESSAGE Editor could not be initialized.
!STACK 0
java.lang.NullPointerException
at org.eclipse.pde.internal.ui.editor.PDEFormEditor.isDirty
(PDEFormEditor.java:310)
at
org.eclipse.pde.internal.ui.editor.PDEFormEditorContributor$SaveAction.update
(PDEFormEditorContributor.java:110)
at
org.eclipse.pde.internal.ui.editor.PDEFormEditorContributor.updateActions
(PDEFormEditorContributor.java:295)
at
org.eclipse.pde.internal.ui.editor.PDEFormEditor.editorDirtyStateChanged
(PDEFormEditor.java:331)
at org.eclipse.pde.internal.ui.editor.PDEFormEditor.fireSaveNeeded
(PDEFormEditor.java:324)
at org.eclipse.pde.internal.ui.editor.PDESourcePage.firePropertyChange
(PDESourcePage.java:99)
at org.eclipse.ui.texteditor.AbstractTextEditor.initializeTitle
(AbstractTextEditor.java:2618)
at org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput
(AbstractTextEditor.java:2697)
at org.eclipse.ui.texteditor.StatusTextEditor.doSetInput
(StatusTextEditor.java:173)
at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput
(AbstractDecoratedTextEditor.java:1077)
at org.eclipse.ui.editors.text.TextEditor.doSetInput
(TextEditor.java:290)
at org.eclipse.ui.texteditor.AbstractTextEditor$14.run
(AbstractTextEditor.java:2141)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread
(ModalContext.java:302)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
at org.eclipse.jface.window.ApplicationWindow$1.run
(ApplicationWindow.java:576)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:84)
at org.eclipse.jface.window.ApplicationWindow.run
(ApplicationWindow.java:573)
at org.eclipse.ui.internal.WorkbenchWindow.run
(WorkbenchWindow.java:1678)
at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit
(AbstractTextEditor.java:2155)
at org.eclipse.ui.texteditor.AbstractTextEditor.init
(AbstractTextEditor.java:2173)
at org.eclipse.ui.part.MultiPageEditorPart.addPage
(MultiPageEditorPart.java:117)
at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:150)
at org.eclipse.pde.internal.ui.editor.MultiSourceEditor.addSourcePage
(MultiSourceEditor.java:29)
at org.eclipse.pde.internal.ui.editor.plugin.ManifestEditor.addPages
(ManifestEditor.java:204)
at org.eclipse.ui.forms.editor.FormEditor.createPages
(FormEditor.java:113)
at org.eclipse.pde.internal.ui.editor.PDEFormEditor.createPages
(PDEFormEditor.java:130)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl
(MultiPageEditorPart.java:187)
at org.eclipse.ui.internal.PartPane$1.run(PartPane.java:93)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:604)
at org.eclipse.core.runtime.Platform.run(Platform.java:545)
at org.eclipse.ui.internal.PartPane.createChildControl(PartPane.java:89)
at org.eclipse.ui.internal.PartPane.createControl(PartPane.java:150)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection
(PartStack.java:659)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:649)
at org.eclipse.ui.internal.EditorWorkbook.setSelection
(EditorWorkbook.java:131)
at org.eclipse.ui.internal.EditorWorkbook.setVisibleEditor
(EditorWorkbook.java:232)
at org.eclipse.ui.internal.EditorPresentation.setVisibleEditor
(EditorPresentation.java:287)
at org.eclipse.ui.internal.EditorPresentation.openEditor
(EditorPresentation.java:227)
at org.eclipse.ui.internal.EditorManager$2.run(EditorManager.java:550)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:84)
at org.eclipse.ui.internal.EditorManager.createEditorTab
(EditorManager.java:539)
at org.eclipse.ui.internal.EditorManager.openInternalEditor
(EditorManager.java:635)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor
(EditorManager.java:438)
at org.eclipse.ui.internal.EditorManager.openEditor
(EditorManager.java:426)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor
(WorkbenchPage.java:2146)
at org.eclipse.ui.internal.WorkbenchPage.access$6
(WorkbenchPage.java:2089)
at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2076)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:84)
at org.eclipse.ui.internal.WorkbenchPage.openEditor
(WorkbenchPage.java:2071)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:265)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor
(EditorUtility.java:137)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor
(EditorUtility.java:110)
at org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open
(OpenActionUtil.java:49)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:161)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:147)
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.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen
(PackageExplorerActionGroup.java:327)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open
(PackageExplorerPart.java:302)
at org.eclipse.jface.viewers.StructuredViewer$2.run
(StructuredViewer.java:400)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:604)
at org.eclipse.core.runtime.Platform.run(Platform.java:545)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen
(StructuredViewer.java:398)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen
(StructuredViewer.java:596)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen
(StructuredViewer.java:685)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent
(OpenStrategy.java:211)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:206)
at org.eclipse.jface.util.OpenStrategy$1.mouseSelectItem
(OpenStrategy.java:359)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent
(OpenStrategy.java:300)
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.Display.runDeferredEvents(Display.java:2594)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2272)
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:140)
at org.eclipse.ui.internal.ide.IDEApplication.run
(IDEApplication.java:90)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run
(PlatformActivator.java:283)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:242)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:119)
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:700)
at org.eclipse.core.launcher.Main.main(Main.java:684) | normal | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08b1'} | 61,011 | Motivation:
I am currently working on a project which represents a framework, and I am using
some sources (general classes) in a separate project.
So I thought the natural solution was to create a linked resource instead of
copying the classes over (I'm still working on the general-use-classes, so that
would involve unnecessary synchronisation-overhead).
Sadly this seems impossible, as Eclipse only allows to link to a resource which
has a direct parent, and I constantly get an error when trying to link to the
classfile from the other project (it IS in a project, but inside a package-tree).
Is this intended or am I doing something wrong?
The only workaround seems to be to create a 3rd project which only contains the
general classes, but that's really a bit kludgy IMO, so I would really prefer if
Eclipse was not so strict and unflexible concerning linked resources...
(of course when exporting the final JAR, the linked resource would have to be
included as as copy anyway, but during development, I'd like it to be linked to
the original files). | enhancement | RESOLVED | DUPLICATE |
{'$oid': '52e9c10f54dc1c25ebdc08b2'} | 61,009 | I've restarted my existing workspace with build 0505.
It took around 12 minutes. The stack dump below (which happens to be
incomplete for some reason) shows a deep recursion.
I have feature projects in my workspace, other team members without feature
projects don't have this problem.
I've attached the stacktrace (it is too long for bugzilla) | critical | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08b3'} | 60,996 | Using AJDT 1.1.8 with Eclipse 3.0 M8, I was in the middle of a refactoring
dialog while an automatically started background build was occurring for my
AspectJ project. I switched focus to another window and got a huge number of
error messages "User Interface is Blocked". See attached screen snapshot. I
had a similar problem occur before; let me know if you need help in isolating
this problem. | normal | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08b4'} | 61,012 | I am developing a plugin, my plugin has infopops in a separate plugin.
I have just moved to milestone 8 with it's new intro view containing context
help.
When my plugin runs I get the attached error
- it appears that it is trying to put my infopop information into the new
view but it is failing.
If I remove the intro view before I show my plugin view it works. If I remove
my inforpop plugin and leave the intro view there then my plugin also works. | normal | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08b5'} | 61,015 | in the follwing file move the interface "MoveMe" into the interface F
----------------------------------------
package a;
interface F
{
}
public class B implements F
{
interface MoveMe //move this interface into F
{
int CONSTANT = -1;
}
}
-----------------------------------------------------------
you get an erroneous warning stating "Only "public static" types and "public
static final" fields with variable intilaizers can be moved into an interface."
Although the warning is correct it does not apply to case above. | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c10f54dc1c25ebdc08b6'} | 61,013 | Build 20040504
As we do support minimal behavior for units outside the classpath (or in non
Java projects), we could better support units outside the workspace.
These are now available through Open External File menu.
2 options:
- allow to create some special fake project (as we do with special fake pkg
roots when outside classpath). Need to filter this special project out from
standard model.
- enrish the working copy owner to allow it to define its classpath and
compiler settings to use (when none is available by default).
Either option have the nice advantage that existing APIs would not need to be
modified. | normal | VERIFIED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08b7'} | 61,016 | Build I200405050200
Using my old workspace, I am not able to add an extension location. I have a
directory containing "plugins" and "features" subdirectories as well as a
".eclipseextension" file. When I try to add it this as an Extension Location, I
get "Selected location does not contain an extension location. Please select
another location".
(I wasn't able to start it at all with a fresh workspace.) | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c10f54dc1c25ebdc08b8'} | 61,014 | When restoring a crashed workspace the AllTypeCache Updater has shown-up
during the start-up sequence before an event loop is active.
The suspicion is that this updating is triggered by a delta before the
runnable that triggers the initial population is executed.
The solution we have discussed is that the all types cache should ignore
deltas and not start updating before the runnable is executed. | normal | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08b9'} | 61,017 | This use-case is pretty wild, but it seems that the refactoring doesn't handle
it well. Or at least it's not clear to me. Consider a java file containing
following two class definitions:
class A {
public B b; // <- rename this
public void method() {
B.b.a.b = null;
}
}
class B {
public static B b;
public A a;
}
Now use the refactoring functionality to rename the marked field (A.b) to
something else, for example "c".
No warnings in the preview, but you can see that the result is not compilable,
as the field reference in method (which is pretty obfuscated) is not updated.
BUT - if you now try to rename the field (now A.c) to "d", it goes fine...
BUT no. 2 - if you now try to rename the field (now A.d) back to "b", you get a
warning in the preview dialog. But if you proceed, the result is OK.
Is this some issue of JDT or am _I_ seeing something wrong? | minor | VERIFIED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08ba'} | 61,018 | Using I20040428 also in I200405040800.
Open Ant Editor for new file.
Add the following text:
<project name="Test" default="run" basedir=".">
<target name="run">
<ant antfile="build.xml" target="foo" />
</target>
</project>
Select and highlight the word "foo". Ctrl+C to copy.
Select and highlight the word "run". Ctrl+V to paste.
2 additional tabs are also inserted.
PB | normal | VERIFIED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08bb'} | 61,019 | I.e. if the view has action that is binded to the Del key text widget that was
placed there will try to invoke action instead of deleting one letter as
supposed. If you will rebind this action to the letter "a" you won't be able
to type this letter. Ctrl+Z, Ctrl+V etc. also work globally (while I would
prefer platform behavior) | major | VERIFIED | INVALID |
{'$oid': '52e9c10f54dc1c25ebdc08bc'} | 61,020 | Build 20040428
It is quite misleading to look for templates in 2 different places in
preference. Some are under editor templates, some are under code style.
From an end-user point of view, these are just Java templates. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c10f54dc1c25ebdc08bd'} | 61,022 | Build 20040428
The comment associated by default to overriding method declarations should
quit dumping a block comment. It should default to generating a true javadoc
comment. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c10f54dc1c25ebdc08be'} | 61,021 | Build 20040428
The shortcut for the NON-NLS is too long to type. Why not simply: "nls" ?
This is the one we had defined when no default was provided. | trivial | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08bf'} | 61,023 | It seems to me that executables are handled in some special way by Windows.
This behavior causes Program.getImageData() to return null for them. But
standard icon for exe files in Windows applications (Explorer) is blue window
frame.
Is it possible for SWT Program to behave as it Explorer does for executables
without embeded icons? | normal | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08c0'} | 61,025 | The API lets you list features that are enabled in the configuration, but not
those installed in sites that the config knows about that are not enabled.
This can be seen in the Product Configuration dialog when you select the
disabled features toggle.
Use case is an ISV trying to install their software on a target product who
checks for their pre-reqs up front. They can only see configured features so
they say no - we can't install or worse, install the missing features again.
If they could list disabled features then after the first search they could ask
again - is the feature there but disabled?
The API should either add an option to the current command, or a new command.
Maybe the implementation should be a list all features and each includes an
attribute (prefix or suffix) that identifies state.
Maybe it should be:
-command allFeatures
I don't see this as an option on the API doc page:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-
home/doc/working/documentation/standalone_update.html | enhancement | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08c2'} | 61,026 | M8 and around there you could use the product config dialog to add an extension
site. It required the .eclipseextnsion file in the eclipse dir (or we were
warned that it would be soon). All fine.
I just grabbed 0504 and tried the above. I had been browsing to my target dir:
d:\mystuff\eclipse and saying go. This no longer works in 0504. I have to
browse to d:\mystuff instead.
I remember text flying by that said if we forgot the \eclipse on the command
API that you would add it. But I did not take that to mean that we could not
add it ourselves (at least in the UI).
If both d:\mystuff\eclipse and d:\mystuff are accepted (assuming that
\eclipse\.eclipseextension exists) that is fine. But seems wrong that you
started to refuse d:\mystuff\eclipse. | normal | RESOLVED | FIXED |
{'$oid': '52e9c10f54dc1c25ebdc08c3'} | 61,027 | I think it would be very useful if the platform logged a build number/id and
version to the platform log file session info (along with java version and
command-line arguments). At least when reporting errors to Eclipse.
But maybe there are some issues (primary feature etc.) which make this
difficult? | minor | RESOLVED | DUPLICATE |
{'$oid': '52e9c11054dc1c25ebdc08c4'} | 61,028 | Actually several things say to me that it is loaded and configured properly but
to end users its as if the feature was disabled.
Info:
-this is a 2.1.X feature so it runs in compatability mode
-The feature has loaded successfully into the previous intergation build
- Looking at the properties of the feature in the "Product Configuration"
dialog I see "The feature is configured properly."
- "Feature Details" shows the feature but the Provider and Feature Name are
blank.
- from "Feature Details" click "Plugin Details" and one plugin is missing (a
docs plugin)
- The Plug-ins view shows only 2 of the 5 plugins in the feature
I will attach the System Summary info shortly.
Geoff | normal | RESOLVED | INVALID |
{'$oid': '52e9c11054dc1c25ebdc08c5'} | 61,030 | Currently, needsRebuild() causes only rebuild of incremental compilation and
full rebuild of all projects (Project->Rebuild All). Full compilation of a
single project runs only once and stops, needsRebuild() has no effect in this
case.
The reason is that incremental compilation and total rebuild are performed in
a loop implemented in BuildManager.basicBuildLoop(...) method that takes
rebuild request into account. Whereas a single project rebuild ends in
BuildManager.build(IProject project, int trigger, IProgressMonitor monitor)
method that ignores needsRebuild() request. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c11054dc1c25ebdc08c6'} | 61,029 | I cannot start my development workspace using I200405050200
The CPU goes up to 100% for several minutes. When I look at the stack dump (see
attached file) it looks as if it's in PDE. After a while I get a StackOverflow
exception and I have to exit.
I then started again with previous build. Closed all perspectives. Exited.
Restarted ==> OK. Opened Java perspective ==> StackOverflow | blocker | RESOLVED | DUPLICATE |
{'$oid': '52e9c11054dc1c25ebdc08c7'} | 61,031 | I rearranged my .java files into new packages. Tried to fix the import
statements with ctrl+shift+O. This worked in some classes, not in others.
Sometimes the import statement would be correctly suggested by the JDT but still
flagged as incorrect by the editor. After much back and forth the import
statement: import view.SwingApp; was accepted, but the class SwingApp still
flagged as not being recognized. Finally the deletion of the import statement
and re-generating with right-click - source - organize imports fixed the
problem. My boss said that this bug is also in Eclipse 2.1.3. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c11054dc1c25ebdc08c8'} | 61,033 | Code generation should produce import statements when dropping beans, and avoid
fully qualifying classes whenever possible. This would make the source code
produced by the VE much easier to read.
Would add:
import javax.swing.JFrame;
and remove the javax.swing. before every reference to a JFrame. | major | CLOSED | FIXED |
{'$oid': '52e9c11054dc1c25ebdc08c9'} | 61,034 | I20040505
public boolean visit(TryStatement node) {
node.catchClauses();
}
assigne node.catchClauses to new local. You get
node.catcthis.node= no;
hClauses(); | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c11054dc1c25ebdc08ca'} | 61,035 | The functionality of attracting user's attention by making a hidden view's
title bold is cool.
However I find that confusing in case when the Problems view is actually
updated to show nothing. Seeing the bold title, I'm truly attracted to go and
see what problems are there and then get confused that there are none.
BTW when experimenting with this "title bolding" feature, it seemed to me that
it doesn't work 100%. My test case was: 2 java projects in workspace, one with
compilation problems, the other with none, default layout of the PDE
perspective, Problems view filtered by project ("any resource in the same
project"). I've been changing the selected project in Package Explorer and
jumping from Problems view to Error log view, all at once, various order and
combinations. Time to time I haven't got the Problems view title bold when
changing the selected project and the view was hidden (but when going to the
Problems view it was showing the correct problems).
Using E3.0M8 (200403261517). | trivial | RESOLVED | DUPLICATE |
{'$oid': '52e9c11054dc1c25ebdc08cb'} | 61,036 | When the Progress view is torn off to be displayed in a separate window it won't
get always refreshed properly.
Steps to reproduce:
1. In the current perspective tear off the Progress view.
2. Switch to another perspective.
3. Bring the Progress view to the foreground, but do NOT tear it off. Make sure
it is visible.
4. Switch back to the first perspective. -> The progress view will show only
background color. When doing something (say, a CVS check-out), it won't show any
progress, rendering it unusable.
I'm seeing this consistently with 3.0 M8 on linux-gtk2. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c11054dc1c25ebdc08cc'} | 61,037 | build i0505-0200
I got the following exceptions in my console when doing a scheduled synchronize
when I first started this new build.
I'm not sure if the fragment project was sucessfully refreshed or not. Other
projects on that server (ottcvs1) seemed to complete ok. (although I don't have
any incoming changes so I don't know for sure)
!SESSION May 05, 2004 08:16:29.447 ---------------------------------------
------
java.version=1.4.2
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -showlocation
!ENTRY org.eclipse.team.core 4 -6 May 05, 2004 08:16:29.447
!MESSAGE CVS Workspace
!SUBENTRY 1 org.eclipse.team.core 4 0 May 05, 2004 08:16:29.457
!MESSAGE An error occurred refreshing /org.eclipse.core.resources.spysupport: Au
thentication error: com.jcraft.jsch.JSchException: Auth fail
!STACK 1
org.eclipse.team.internal.ccvs.core.connection.CVSAuthenticationException: Authe
ntication error: com.jcraft.jsch.JSchException: Auth fail
at org.eclipse.team.internal.ccvs.ssh2.CVSSSH2ServerConnection.open(CVSS
SH2ServerConnection.java:133)
at org.eclipse.team.internal.ccvs.core.connection.Connection.open(Connec
tion.java:127)
at org.eclipse.team.internal.ccvs.core.connection.CVSRepositoryLocation.
createConnection(CVSRepositoryLocation.java:568)
at org.eclipse.team.internal.ccvs.core.connection.CVSRepositoryLocation.
openConnection(CVSRepositoryLocation.java:819)
at org.eclipse.team.internal.ccvs.core.client.Session.open(Session.java:
142)
at org.eclipse.team.internal.ccvs.core.resources.RemoteFolderTreeBuilder
.fetchDelta(RemoteFolderTreeBuilder.java:219)
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.getRem
oteTree(CVSWorkspaceRoot.java:230)
at org.eclipse.team.internal.ccvs.core.syncinfo.CVSResourceVariantTree.f
etchVariant(CVSResourceVariantTree.java:95)
at org.eclipse.team.core.variants.AbstractResourceVariantTree.refresh(Ab
stractResourceVariantTree.java:107)
at org.eclipse.team.core.variants.AbstractResourceVariantTree.refresh(Ab
stractResourceVariantTree.java:67)
at org.eclipse.team.core.variants.ResourceVariantTreeSubscriber.refresh(
ResourceVariantTreeSubscriber.java:157)
at org.eclipse.team.core.variants.ResourceVariantTreeSubscriber.refresh(
ResourceVariantTreeSubscriber.java:123)
at org.eclipse.team.internal.ui.synchronize.RefreshSubscriberJob.runInWo
rkspace(RefreshSubscriberJob.java:207)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(Internal
WorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
!SUBENTRY 2 org.eclipse.team.cvs.core 4 2 May 05, 2004 08:16:29.467
!MESSAGE Authentication error: com.jcraft.jsch.JSchException: Auth fail | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11054dc1c25ebdc08cd'} | 61,038 | When pressing down at the bottom of the list you
could wrap-around to the first item in the list. I understand that home/end
are already supported, but this is the behaviour supported in code assist and
I got used to it. | normal | VERIFIED | FIXED |
{'$oid': '52e9c11054dc1c25ebdc08ce'} | 61,039 | Color buttons for background and foreground need MSAA name, and need to be
associated with their nearby labels. With MS Inspect Objects, the current MSAA
name is "none". It should be "Background [or foreground] for completion
proposals".
OR: If the button is made to be in a grouping headed by "Background for
completion proposals" then the button can also have "Color selector". This
would cause JAWS to read the grouping, and then the MSAA name. | normal | RESOLVED | FIXED |
{'$oid': '52e9c11054dc1c25ebdc08cf'} | 61,040 | Build 20040428
This is the counterpart of bug 60437 in JDTCore.
We should be internally setting the resolved classpath to an empty path, while
computing the resolvedClasspath itself, since we are going to call out to
client code when requesting container entries.
If client is misbehaving, then infinite recursion will occur. | normal | VERIFIED | FIXED |
{'$oid': '52e9c11054dc1c25ebdc08d0'} | 61,041 | Request placed by Sian to handle expand(CompoundQuery) in panther's query
language. | enhancement | RESOLVED | FIXED |
{'$oid': '52e9c11054dc1c25ebdc08d1'} | 61,042 | In the Code Templates preferences page, select a template and press "Edit". In
the "Edit Template" dialog, press "Insert Variable". Can't escape out of the
popup back to the "Edit Template" dialog without using the mouse. | normal | VERIFIED | INVALID |
{'$oid': '52e9c11054dc1c25ebdc08d2'} | 61,044 | CDT 2.0.0.200404281729
Eclipse 200404281424
The SRS states that users can expect to see search results as they are found.
This is currently not the case. | major | VERIFIED | FIXED |
{'$oid': '52e9c11054dc1c25ebdc08d3'} | 61,043 | From C/C++ Code Templates preference page, press "New". In the "New Template"
hit Alt+p. This should bring focus to the Pattern input area, but focus stays
where it is. | normal | VERIFIED | FIXED |
{'$oid': '52e9c11054dc1c25ebdc08d4'} | 61,045 | In the Code Templates preference page, tab to the Preview area. In MS Inspect
Objects, the MSAA name shows "none". It should be "Preview". | normal | RESOLVED | FIXED |
{'$oid': '52e9c11154dc1c25ebdc08d5'} | 61,046 | Build I200505050200
When I click on a stackframe within any classes from imported plugins, I get the
"Source file not found" editor. The classes are contained in a jar with source
attachment listed under my project's "Plug-in Dependencies". This used to work
before, and I can open it correctly in the Java Perspective. | normal | VERIFIED | FIXED |
{'$oid': '52e9c11154dc1c25ebdc08d6'} | 61,048 | In a team of developers all trying to use an identical eclipse configuration, it's
a pain trying to keep them synchronized. If Eclipse itself could incorporate CVS
control of its own config, this would make things much easier.
This would most likely involve a setting where you specify the CVS repository and
module to use, and then an "update from CVS" action to grab the latest config,
perhaps even with an auto-update feature (on startup?) | enhancement | RESOLVED | WORKSFORME |
{'$oid': '52e9c11154dc1c25ebdc08d7'} | 61,050 | The keys preference page is creating colors without disposing them (see the end
of the buildKeySequenceAssignmentTable() and buildCommandAssignmentTable()
methods). Additionally, it's hardcoding this color to be medium grey which.
Hardcoding bad, system colors good. | major | RESOLVED | FIXED |
{'$oid': '52e9c11154dc1c25ebdc08d8'} | 61,047 | when the list of projects selected is large the clean dialog will attempt to
show as much of the text as possible. I think this looks a little crazy. The
dialog should limit itself to 2/3 of the monitor width or something. | normal | RESOLVED | FIXED |
{'$oid': '52e9c11154dc1c25ebdc08d9'} | 61,049 | Using 200405050200, you can see a gray circle in front of the job. This looks
like a missing icon or an icon that is not rendered properly.
See attached screenshot | normal | RESOLVED | FIXED |
{'$oid': '52e9c11154dc1c25ebdc08da'} | 61,051 | I20040505
The keybinding for Step into (F5) is not working. This was mentioned in bug
60881, but I could not find a new bug report for it. | normal | VERIFIED | DUPLICATE |
{'$oid': '52e9c11154dc1c25ebdc08db'} | 61,052 | I20040505
While investigating bug 57181, we noticed that the container initialization
can be highly recursive if clients missbehave. This can potential blow the
stack and cause a StackOverflowError.
We should protect ourselves against such clients and flatten the container
initialization. | normal | VERIFIED | FIXED |
{'$oid': '52e9c11154dc1c25ebdc08dc'} | 61,054 | When the user starts making changes to the checkbox tree, the Radio mode of the
synchronize should switch immediately to "Selected Resources".
Alternatively, the Tree should be disabled until "SelectedResources" is chosen. | normal | RESOLVED | FIXED |
{'$oid': '52e9c11154dc1c25ebdc08dd'} | 61,056 | Using build I200405050200, I got following error message in log when I hit 'F5'
key in 'Debug' view:
!ENTRY org.eclipse.ui 4 4 May 05, 2004 16:25:12.39
!MESSAGE Conflicting key binding for 'org.eclipse.ui.file.refresh' and
'org.eclipse.debug.ui.commands.StepInto'
Conflicting key binding for 'org.eclipse.ui.file.refresh' and
'org.eclipse.debug.ui.commands.StepInto' | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11154dc1c25ebdc08de'} | 61,055 | normal | CLOSED | FIXED |
|
{'$oid': '52e9c11154dc1c25ebdc08df'} | 61,057 | 20040505 self hosted with the platfrom-ui module loaded from HEAD
!ENTRY org.eclipse.ui.ide 4 4 May 05, 2004 10:30:46.534
!MESSAGE Problems saving workspace
!ENTRY org.eclipse.ui.ide 2 1 May 05, 2004 10:30:46.549
!MESSAGE Problems occurred while trying to save the state of the workbench.
!SUBENTRY 1 org.eclipse.core.resources 2 566 May 05, 2004 10:30:46.549
!MESSAGE Problems occurred during save.
!STACK 0
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782)
at java.util.HashMap$KeyIterator.next(HashMap.java:818)
at org.eclipse.jdt.internal.core.JavaModelManager.saving
(JavaModelManager.java:1409)
at org.eclipse.core.internal.resources.SaveManager.executeLifecycle
(SaveManager.java:308)
at org.eclipse.core.internal.resources.SaveManager$1.run
(SaveManager.java:129)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:604)
at org.eclipse.core.runtime.Platform.run(Platform.java:545)
at org.eclipse.core.internal.resources.SaveManager.broadcastLifecycle
(SaveManager.java:141)
at org.eclipse.core.internal.resources.SaveManager.save
(SaveManager.java:1323)
at org.eclipse.core.internal.resources.Workspace.save
(Workspace.java:1690)
at org.eclipse.ui.internal.ide.IDEWorkbenchAdvisor$5.run
(IDEWorkbenchAdvisor.java:468)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread
(ModalContext.java:302)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run
(ProgressMonitorDialog.java:397)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run
(ProgressMonitorJobsDialog.java:237)
at
org.eclipse.ui.internal.ide.IDEWorkbenchAdvisor.disconnectFromWorkspace
(IDEWorkbenchAdvisor.java:475)
at org.eclipse.ui.internal.ide.IDEWorkbenchAdvisor.postShutdown
(IDEWorkbenchAdvisor.java:231)
at org.eclipse.ui.internal.Workbench.shutdown(Workbench.java:1618)
at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:458)
at org.eclipse.ui.internal.Workbench.access$8(Workbench.java:389)
at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:561)
at org.eclipse.swt.custom.BusyIndicator.showWhile
(BusyIndicator.java:84)
at org.eclipse.ui.internal.Workbench.close(Workbench.java:559)
at org.eclipse.ui.internal.Workbench.close(Workbench.java:535)
at org.eclipse.ui.internal.QuitAction.run(QuitAction.java:55)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
(ActionContributionItem.java:612)
at org.eclipse.jface.action.ActionContributionItem.access$2
(ActionContributionItem.java:563)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent
(ActionContributionItem.java:482)
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.Display.runDeferredEvents(Display.java:2594)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2272)
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:140)
at org.eclipse.ui.internal.ide.IDEApplication.run
(IDEApplication.java:90)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run
(PlatformActivator.java:283)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:242)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:119)
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:700)
at org.eclipse.core.launcher.Main.main(Main.java:684) | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11154dc1c25ebdc08e0'} | 61,058 | Steps:
1 - From the test results page for any build (whose tests were run), open the
Unit tests for Core (org.eclipse.core.tests_winxp | linux.gtk), or just go
directly today's build results for Core on Windows XP:
http://download.eclipse.org/downloads/drops/I-I20040505-200405050200/testresults/html/org.eclipse.core.tests_winxp.html
3 - Try any of the local links (links pointing to the same page). They don't
work. It seems to be because the destination anchors have "#name" as name when
they should just have "name" (the "#name" notation should be used only in URIs
in source anchors). Of course, IE accepts them, but that is not anywhere in the
HTML spec (http://www.w3.org/TR/html4/struct/links.html#h-12.1). | normal | RESOLVED | FIXED |
{'$oid': '52e9c11154dc1c25ebdc08e1'} | 61,059 | 20040505
MESSAGE Conflicting key binding for 'org.eclipse.ui.file.refresh'
and 'org.eclipse.debug.ui.commands.StepInto' | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11154dc1c25ebdc08e2'} | 61,032 | Not at all in M8, better but not yet there in 0504.
Base definition is:
<feature
id="com.ibm.jdg2e.exercises"
label="com.ibm.jdg2e.exercises"
version="1.0.0"
provider-name=""
primary="true"
plugin="com.ibm.lab.tool.pkg">
Branding in a plugin with an id that does not match feature.
In m8 there is no listing in the feature details dialog for the jdg2e.exercises
feature (unbranded feature response).
In 0504 it is there, but with data missing (no feature icon, no name, no
details when selected).
Works fine if the feature and plugin ids match.
Backed the definition being used over to a 2.1.1 build and it works fine there
(full branding with alt plugin id). | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11154dc1c25ebdc08e3'} | 61,060 | 20040505
Having multiple editors open, the tab gets quite small and the label is shortend
and gets less useful.
I think there is still room for improvement: Why not having the lable going
right at the right edge and have the close symbol 'X' render over the label
(=the dots)
The 'X' only shows up when the mouse is pointer is near.
Also it could make sense to only use two dots | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11154dc1c25ebdc08e4'} | 61,061 | If I bring up eclipse with the -data argument pointing to a directory on the
Andrew File System (AFS), eclipse fails with the message:
Error in runtime: workspace cannot be set. Exiting.
If I look in the workspace directory there is a .metadata directory created.
inside it there is .lock file and nothing else.
If I just change the invocation of eclipes to put the workspace in the local
file space (or in DFS) then eclipse comes up just fine. | normal | RESOLVED | INVALID |
{'$oid': '52e9c11154dc1c25ebdc08e5'} | 61,062 | Using 200405050200, I tried to remove the dependency to runtime.compatibility
for our tests.
In the classes org.eclipse.jdt.core.tests.model.AbstractJavaModelTests and
org.eclipse.jdt.core.tests.formatter.FormatterRegressionTests, I replaced the
getPluginDirectoryPath() method with:
/**
* Returns the OS path to the directory that contains this plugin.
*/
protected String getPluginDirectoryPath() {
try {
URL platformURL =
Platform.getBundle("org.eclipse.jdt.core.tests.model").getEntry("/");
return new File(Platform.asLocalURL(platformURL).getFile()).getAbsolutePath();
} catch (IOException e) {
e.printStackTrace();
}
return null;
}
Then I can still run the tests using the JUnit plugin tests launching
configuration.
I removed the dependency to org.eclipse.core.runtime.compatibility from the list
of requires plugins.
Then I cannot run the tests anymore. It looks like it cannot find the tests to
run. Starting with -console and using the command 'ss', I can see that the
plugin org.eclipse.jdt.core.tests.model is resolved. | normal | RESOLVED | INVALID |
{'$oid': '52e9c11154dc1c25ebdc08e6'} | 61,063 | build I20040505 2am.
there was an error in the java editor opening a file, however after this error
occured we still try to give focus to this editor and get into an infinite
loop.. .see stack trace below
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:4120)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3012)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3160)
at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
at org.eclipse.swt.widgets.Control.forceFocus(Control.java:599)
at org.eclipse.swt.widgets.Control.setFocus(Control.java:2037)
at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:447)
at org.eclipse.jface.window.ApplicationWindow.run
(ApplicationWindow.java:610)
at org.eclipse.ui.internal.WorkbenchWindow.run
(WorkbenchWindow.java:1678)
at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit
(AbstractTextEditor.java:2155)
at org.eclipse.ui.texteditor.AbstractTextEditor.init
(AbstractTextEditor.java:2173)
at org.eclipse.ui.internal.EditorManager.createSite
(EditorManager.java:569)
at org.eclipse.ui.internal.EditorManager.openInternalEditor
(EditorManager.java:633)
at org.eclipse.ui.internal.EditorManager.access$7
(EditorManager.java:619)
at org.eclipse.ui.internal.EditorManager$7.run(EditorManager.java:798)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:604)
at org.eclipse.core.runtime.Platform.run(Platform.java:545)
at org.eclipse.ui.internal.EditorManager.busyRestoreEditor
(EditorManager.java:773)
at org.eclipse.ui.internal.EditorManager$6.run(EditorManager.java:766)
at org.eclipse.swt.custom.BusyIndicator.showWhile
(BusyIndicator.java:84)
at org.eclipse.ui.internal.EditorManager.restoreEditor
(EditorManager.java:762)
at org.eclipse.ui.internal.EditorManager$Editor.getEditor
(EditorManager.java:1136)
at org.eclipse.ui.internal.EditorManager$Editor.getPart
(EditorManager.java:1128)
at org.eclipse.ui.internal.PartPane.requestActivation
(PartPane.java:246)
at org.eclipse.ui.internal.EditorPane.requestActivation
(EditorPane.java:150)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:226)
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:801)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:913)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:1756)
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:4120)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3012)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3160)
at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
at org.eclipse.swt.widgets.Control.forceFocus(Control.java:599)
at org.eclipse.swt.widgets.Control.setFocus(Control.java:2037)
at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:447)
at org.eclipse.jface.window.ApplicationWindow.run
(ApplicationWindow.java:610)
at org.eclipse.ui.internal.WorkbenchWindow.run
(WorkbenchWindow.java:1678)
at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit
(AbstractTextEditor.java:2155)
at org.eclipse.ui.texteditor.AbstractTextEditor.init
(AbstractTextEditor.java:2173)
at org.eclipse.ui.internal.EditorManager.createSite
(EditorManager.java:569)
at org.eclipse.ui.internal.EditorManager.openInternalEditor
(EditorManager.java:633)
at org.eclipse.ui.internal.EditorManager.access$7
(EditorManager.java:619)
at org.eclipse.ui.internal.EditorManager$7.run(EditorManager.java:798)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:604)
at org.eclipse.core.runtime.Platform.run(Platform.java:545)
at org.eclipse.ui.internal.EditorManager.busyRestoreEditor
(EditorManager.java:773)
at org.eclipse.ui.internal.EditorManager$6.run(EditorManager.java:766)
at org.eclipse.swt.custom.BusyIndicator.showWhile
(BusyIndicator.java:84)
at org.eclipse.ui.internal.EditorManager.restoreEditor
(EditorManager.java:762)
at org.eclipse.ui.internal.EditorManager$Editor.getEditor
(EditorManager.java:1136)
at org.eclipse.ui.internal.EditorManager$Editor.getPart
(EditorManager.java:1128)
at org.eclipse.ui.internal.PartPane.requestActivation
(PartPane.java:246)
at org.eclipse.ui.internal.EditorPane.requestActivation
(EditorPane.java:150)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:226)
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:801)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:913)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:1756)
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:4120)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3012)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3160)
at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
at org.eclipse.swt.widgets.Control.forceFocus(Control.java:599)
at org.eclipse.swt.widgets.Control.setFocus(Control.java:2037)
at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:447)
at org.eclipse.jface.window.ApplicationWindow.run
(ApplicationWindow.java:610)
at org.eclipse.ui.internal.WorkbenchWindow.run
(WorkbenchWindow.java:1678)
at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit
(AbstractTextEditor.java:2155)
at org.eclipse.ui.texteditor.AbstractTextEditor.init
(AbstractTextEditor.java:2173)
at org.eclipse.ui.internal.EditorManager.createSite
(EditorManager.java:569)
at org.eclipse.ui.internal.EditorManager.openInternalEditor
(EditorManager.java:633)
at org.eclipse.ui.internal.EditorManager.access$7
(EditorManager.java:619)
at org.eclipse.ui.internal.EditorManager$7.run(EditorManager.java:798)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:604)
at org.eclipse.core.runtime.Platform.run(Platform.java:545)
at org.eclipse.ui.internal.EditorManager.busyRestoreEditor
(EditorManager.java:773)
at org.eclipse.ui.internal.EditorManager$6.run(EditorManager.java:766)
at org.eclipse.swt.custom.BusyIndicator.showWhile
(BusyIndicator.java:84)
at org.eclipse.ui.internal.EditorManager.restoreEditor
(EditorManager.java:762)
at org.eclipse.ui.internal.EditorManager$Editor.getEditor
(EditorManager.java:1136)
at org.eclipse.ui.internal.EditorManager$Editor.getPart
(EditorManager.java:1128)
at org.eclipse.ui.internal.PartPane.requestActivation
(PartPane.java:246)
at org.eclipse.ui.internal.EditorPane.requestActivation
(EditorPane.java:150)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:226)
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:801)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:913)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:1756)
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:4120)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3012)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3160)
at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
at org.eclipse.swt.widgets.Control.forceFocus(Control.java:599)
at org.eclipse.swt.widgets.Control.setFocus(Control.java:2037)
at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:447)
at org.eclipse.jface.window.ApplicationWindow.run
(ApplicationWindow.java:610)
at org.eclipse.ui.internal.WorkbenchWindow.run
(WorkbenchWindow.java:1678)
at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit
(AbstractTextEditor.java:2155)
at org.eclipse.ui.texteditor.AbstractTextEditor.init
(AbstractTextEditor.java:2173)
at org.eclipse.ui.internal.EditorManager.createSite
(EditorManager.java:569)
at org.eclipse.ui.internal.EditorManager.openInternalEditor
(EditorManager.java:633)
at org.eclipse.ui.internal.EditorManager.access$7
(EditorManager.java:619)
at org.eclipse.ui.internal.EditorManager$7.run(EditorManager.java:798)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:604)
at org.eclipse.core.runtime.Platform.run(Platform.java:545)
at org.eclipse.ui.internal.EditorManager.busyRestoreEditor
(EditorManager.java:773)
at org.eclipse.ui.internal.EditorManager$6.run(EditorManager.java:766)
at org.eclipse.swt.custom.BusyIndicator.showWhile
(BusyIndicator.java:84)
at org.eclipse.ui.internal.EditorManager.restoreEditor
(EditorManager.java:762)
at org.eclipse.ui.internal.EditorManager$Editor.getEditor
(EditorManager.java:1136)
at org.eclipse.ui.internal.EditorManager$Editor.getPart
(EditorManager.java:1128)
at org.eclipse.ui.internal.PartPane.requestActivation
(PartPane.java:246)
at org.eclipse.ui.internal.EditorPane.requestActivation
(EditorPane.java:150)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:226)
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:801)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:913)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:1756)
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:4120)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3012)
!ENTRY org.eclipse.core.runtime 4 2 May 05, 2004 10:52:28.440
!MESSAGE Problems occurred when invoking code from plug-
in: "org.eclipse.core.runtime".
!STACK 0
java.lang.NullPointerException
at
org.eclipse.jdt.internal.ui.javaeditor.BasicJavaEditorActionContributor.setActi
veEditor(BasicJavaEditorActionContributor.java:242)
at
org.eclipse.jdt.internal.ui.javaeditor.BasicEditorActionContributor.setActiveEd
itor(BasicEditorActionContributor.java:83)
at
org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditorActionContributor.s
etActiveEditor(CompilationUnitEditorActionContributor.java:59)
at org.eclipse.ui.internal.EditorActionBars.partChanged
(EditorActionBars.java:291)
at org.eclipse.ui.internal.WorkbenchPage$2.run(WorkbenchPage.java:474)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:604)
at org.eclipse.core.runtime.Platform.run(Platform.java:545)
at org.eclipse.ui.internal.WorkbenchPage.activatePart
(WorkbenchPage.java:466)
at org.eclipse.ui.internal.WorkbenchPage.setActivePart
(WorkbenchPage.java:2596)
at org.eclipse.ui.internal.WorkbenchPage.requestActivation
(WorkbenchPage.java:2307)
at org.eclipse.ui.internal.PartPane.requestActivation
(PartPane.java:246)
at org.eclipse.ui.internal.EditorPane.requestActivation
(EditorPane.java:150)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:226)
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:801)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:913)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:1756)
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:4120)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3012)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3160)
at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
at org.eclipse.swt.widgets.Control.forceFocus(Control.java:599)
at org.eclipse.swt.widgets.Control.setSavedFocus(Control.java:2262)
at org.eclipse.swt.widgets.Decorations.restoreFocus
(Decorations.java:733)
at org.eclipse.swt.widgets.Decorations.WM_ACTIVATE
(Decorations.java:1477)
at org.eclipse.swt.widgets.Shell.WM_ACTIVATE(Shell.java:1327)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:2949)
at org.eclipse.swt.widgets.Decorations.windowProc
(Decorations.java:1449)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3160)
at org.eclipse.swt.internal.win32.OS.DestroyWindow(Native Method)
at org.eclipse.swt.widgets.Control.destroyWidget(Control.java:504)
at org.eclipse.swt.widgets.Widget.dispose(Widget.java:369)
at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:371)
at org.eclipse.swt.widgets.Shell.dispose(Shell.java:486)
at org.eclipse.jface.window.Window.close(Window.java:253)
at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:811)
at
org.eclipse.ui.internal.ide.dialogs.InternalErrorDialog.buttonPressed
(InternalErrorDialog.java:88)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:491)
at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:89)
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.Display.runDeferredEvents(Display.java:2594)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2272)
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.ide.dialogs.InternalErrorDialog.open
(InternalErrorDialog.java:71)
at org.eclipse.ui.internal.ide.dialogs.InternalErrorDialog.openQuestion
(InternalErrorDialog.java:173)
at org.eclipse.ui.internal.ide.IDEExceptionHandler.openQuestionDialog
(IDEExceptionHandler.java:151)
at org.eclipse.ui.internal.ide.IDEExceptionHandler.handleException
(IDEExceptionHandler.java:83)
at org.eclipse.ui.internal.ide.IDEWorkbenchAdvisor.eventLoopException
(IDEWorkbenchAdvisor.java:230)
at org.eclipse.ui.internal.ExceptionHandler.handleException
(ExceptionHandler.java:53)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1357)
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:140)
at org.eclipse.ui.internal.ide.IDEApplication.run
(IDEApplication.java:90)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run
(PlatformActivator.java:283)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:242)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:119)
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:700)
at org.eclipse.core.launcher.Main.main(Main.java:684) | major | RESOLVED | WORKSFORME |
{'$oid': '52e9c11154dc1c25ebdc08e7'} | 61,064 | We have many string variables that accept arguments (for example,
workspace_loc), but the variable descriptions do not indicate this. Make a
pass of all contributed variables and update descriptions to ensure we doc
which vars accept args. Those that do not accept args should have their
extension definition updated to indicate so (via "supportsArgument="false""). | normal | VERIFIED | FIXED |
{'$oid': '52e9c11254dc1c25ebdc08e8'} | 61,053 | Launching a java app with Full Exectution Collection, and open Object
Interactions view, then Open Class interactions view. The Class interaction
view is not display properly, and it's only partly drawn. The rest of the
drawing is what is residued from the Object Interaction view.
screen shot to be attached | major | CLOSED | FIXED |
{'$oid': '52e9c11254dc1c25ebdc08e9'} | 61,065 | Some variables support an enumeration of arguments (for example the ${system}
variable). We could enhance the extension point to support the enumeration of
valid arguments, with descriptions. This would allow a generic UI to be build
to configure the arguments for a variable. | enhancement | CLOSED | WONTFIX |
{'$oid': '52e9c11254dc1c25ebdc08ea'} | 61,066 | Build I20040505
0. In a workspace with a working SSH repo connection to dev.eclipse.org
1. CVS Repositrories view; select repo; open Properties
2. Change password field to a password of a different length. Hit Apply.
3. Close Properties dialog
4. Reopen Properties dialog
Observe: the password field show the length of the original password.
The behavior of the system shows that the password has not changed.
Expectation: When I change the password, it should take.
I tried variations with pserver repo type, and the Save Password box checked
vs. unchecked. All have the same problem. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c11254dc1c25ebdc08eb'} | 61,068 | Build I20040505
I have projects from more than one CVS repo in my ws. The password on one of
them was wrong. The error message did not identify which repository. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c11254dc1c25ebdc08ec'} | 61,069 | build: 4/23
There does not seem to be a way for a screen reader like JAWS or Window-eyes to
read the error message displayed in org.eclipse.jface.dialogs.InputDialog.
Perhaps the errorMessageLabel should be Read-Only text input so that users can
tab to and read the error message if one exists. | normal | VERIFIED | FIXED |
{'$oid': '52e9c11254dc1c25ebdc08ed'} | 61,067 | This happens on the I20040428 and I20040505. I'm not sure when it started
happening. If I try to export the following projects as deployable plugins I
get compile errors in a log.zip
org.eclipse.core.runtime
org.eclipse.core.runtime.compatibility
org.eclipse.osgi
org.eclipse.osgi.services
org.eclipse.osgi.util
Here are the steps to reproduce:
1. Extract the above projects from HEAD into a workspace.
2. Select all the 5 projects and bring up the export wizard.
3. Select Deployable plugins and fragments, click next.
4. Select a destination zip, click finish.
The three osgi projects appear to compile and build fine but the runtime
project does not seem to compile. I get a logs.zip with compile errors. I
will attach the log.zip file. | normal | RESOLVED | FIXED |
{'$oid': '52e9c11254dc1c25ebdc08ee'} | 61,070 | The following appeared in the log file and the F5 key no longer does a step
into. This is with I20040505
Conflicting key binding for 'org.eclipse.ui.file.refresh'
and 'org.eclipse.debug.ui.commands.StepInto' | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11254dc1c25ebdc08ef'} | 61,071 | build I20040427
OK, this is a hard one to explain.
- I set a breakpoint on MenuItem.setText
- reactivated my target
- the breakpoint was hit immediately
- made it a conditional breakpoint with condition:
"".equals(string)
- resumed
- the workbench resumed (slowly -- the overhead for conditional breakpoints
seems high)
- popped up the context menu in a view
- breakpoint was not hit
- went back and forth a few times between host and target
- breakpoint was not hit, but it was really slowing done the target (it updates
menus in response to window activation and deactivation)
- double-clicked on breakpoint icon to remove it while the target was consuming CPU
- the breakpoint was hit, but the Debug view did not show the stack
- selecting the main thread showed Resume as enabled
- closed and reopened the Debug view
- it showed that the breakpoint had indeed been hit
- the string argument was non-empty ("Ex&tract Interface...") so the breakpoint
should not have been hit
So there seems to be two problems here:
1. It seems like Debug removes the condition before removing the breakpoint, so
it's possible for it to get hit in the interim.
2. When this happens, the Debug view does not update properly.
I also saw a few of these in my log:
org.eclipse.debug.core.DebugException: Breakpoint does not have an associated
marker.
at org.eclipse.debug.core.model.Breakpoint.ensureMarker(Breakpoint.java:264)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.getSuspendPolicy(JavaBreakpoint.java:859)
at
org.eclipse.jdt.internal.debug.core.model.JDIThread.handleSuspendForBreakpoint(JDIThread.java:1040)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.suspend(JavaBreakpoint.java:308)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.suspendForEvent(JavaLineBreakpoint.java:396)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint$EvaluationListener.evaluationComplete(JavaLineBreakpoint.java:556)
at
org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine$EvalRunnable.evaluationFinished(ASTEvaluationEngine.java:381)
at
org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine$EvalRunnable.run(ASTEvaluationEngine.java:376)
at
org.eclipse.jdt.internal.debug.core.model.JDIThread$ThreadJob.run(JDIThread.java:2508)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66) | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c11254dc1c25ebdc08f0'} | 61,072 | Bug 57333 added support for asking a variable if it supports arguments. We should use this support to
provide warnings in the LCD when someone specifies a variable that won't be used. | enhancement | RESOLVED | WONTFIX |
{'$oid': '52e9c11254dc1c25ebdc08f1'} | 61,073 | build i0505-0200, linux-gtk
Not so much of a problem but more of an inconsistency. Perhaps this is just the
difference between the 2 platforms but you guys would know better than me. Is
this how things are supposed to work?
In the Navigator, I wanted to use the keyboard to expand and collapse tree items.
Linux-GTK:
- Node was not expanded when I hit right-arrow.
- Hitting Enter expands and then collapses the node immediately
- Hitting Space expands the node. Hitting it again collapses the node.
Windows:
- right-arrow/left-arrow expand and collapse the node
- space does nothing
- Enter expands the node. Hitting it again collapses the node. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c11254dc1c25ebdc08f2'} | 61,074 | in the new runtime, if a plugin has a manifest.mf, the <plugin> tag in the
plugin.xml need not have ANY attributes. Any attributes that are there are
ignored. Currently the editor marks this as an error.
Related to this, if htere is a manifest.mf, the <runtime> and <requires>
elements in a plugin.xml are ignored. In all of these ignore cases it may be
useful for the editor to warn the user that they have irrelevant entries in the
plugin.xml. Without this, users may update the values in the plugin.xml and
expect them to take effect. | normal | RESOLVED | FIXED |
{'$oid': '52e9c11254dc1c25ebdc08f3'} | 61,076 | build i0505-0200, linux-gtk
- In the context menu in the Java editor, it says that "esc ctrl-F" is the
shortcut for Format.
- "esc ctrl-F" brings up the Find/Replace dialog
- "ctrl-shift-F" (the binding on Windows) doesn't do anything. It actually
prints out an underlined "F" character as many times as you press it, but only
for the duration that you hold down the ctrl and esc keys...when you let them go
the "F" disappears. | normal | VERIFIED | INVALID |
{'$oid': '52e9c11254dc1c25ebdc08f4'} | 61,078 | Currently to implement a radio button group a user has to put it in a separate
composite, which may have undesired layout side effects. I can think of two
possible solutions to this problem:
1. Introduce FIRST_IN_GROUP style for radio button. This is how Windows does
it. This solution is very simple and efficient, but some may find it somewhat
limiting.
2. Introduce a non-visual RadioButtonGroup component containing a list of radio
buttons that belong to the same group. | enhancement | RESOLVED | WONTFIX |
{'$oid': '52e9c11254dc1c25ebdc08f5'} | 61,079 | We request that this bug be included in the M9 code base.
In the core file org.eclipse.core.runtime.adaptor.EclipseStarter.java,
we need the ability to install generic OSGI bundles that exist in the eclipse
direcotry (eg. bundlefiles/mybundle.jar) as part of the startup routine defined
in the "eclipse.properties" file. The format is "file:[bundle-name]@[start
level]", eg.
osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
org.eclipse.core.runtime@2, org.eclipse.update.configurator@3,
file:bundlefiles/eejb.jar@4, file:bundlefiles/java.sql.Package.jar@4,
file:bundlefiles/db2ejdbc+WindowsXP+x86.jar@4
The problem is in searchForBundle() method (line 315): bundlefiles/file.jar is
expected to be a relative path from the eclipse root directory (eg.
c:\eclipse\bundlesfiles\file.jar). It can not be a reference because the
searchFor() call (line 351) will fail as it is not a plugin directory. With the
"file:" in front of the name, result.connect() will throw an IOException because
the URL has the path "bunglefiles/file.jar". The fix from our Beijing team is
to set the URL to same path as the fileLocation.
The patch for this fix follows:
Index: EclipseStarter.java
===================================================================
RCS file:
/home/eclipse/org.eclipse.osgi/eclipseAdaptor/src/org/eclipse/core/runtime/adaptor/EclipseStarter.java,v
retrieving revision 1.51
diff -u -r1.51 EclipseStarter.java
--- EclipseStarter.java 1 May 2004 02:51:35 -0000 1.51
+++ EclipseStarter.java 5 May 2004 15:52:07 -0000
@@ -340,6 +340,10 @@
// if the location is relative, prefix it with the syspath
if (!fileLocation.isAbsolute())
fileLocation = new File(parent, fileLocation.toString());
+// zhangrongsheng 2004/03/09 Add Generic OSGi bundle support
+ if (fileLocation != null)
+ url = new URL("file", null, fileLocation.toString());
+///////////////////////////
}
// If the result is a reference then search for the real result and
// reconstruct the answer. | normal | RESOLVED | FIXED |
{'$oid': '52e9c11254dc1c25ebdc08f6'} | 61,080 | The ClasspathContainerInitializer API has roughly the following flow:
1. Client calls some Java model operation that needs to open a project;
project has classpath container entry on classpath
2. Java model instantiates registered ClasspathContainerInitializer;
calls initialize(containerPath, javaProject)
3. Client code in initialize installs a classpath container by
calling JavaCore.setClasspathContainer()
(containerPath,affectedProjects,respectiveContainers,monitor)
4. Java model changes dynamic project references and reports Java model deltas
This flow is problematic if the triggering operation (1) is an operation that
merely queries the Java model as far as the client is concerned.
The Java model would have more flexibility to defer modifying project
references and reporting Java model deltas if the interaction at step (2) was
to ask instead the client to compute and return a classpath container object,
which the Java model would then be responsible for installing. | normal | RESOLVED | WONTFIX |
{'$oid': '52e9c11254dc1c25ebdc08f7'} | 61,077 | Our SQE engineers have developed a reliability suite recently, and it
includes XEmbed-related testcase. It was convenient for them to
implement one of the sides (embedded - embedder) using SWT.
However, their testcase shows hangs on their machine (unfortunately, I
can't reproduce it locally, because in my environment it crashes). In
both cases we are using SWT-3.0M8, motif-based in my case Operating system, in
both cases, is a development version of Linux. | normal | RESOLVED | WORKSFORME |
{'$oid': '52e9c11254dc1c25ebdc08f8'} | 61,081 | Eclipse build: Version: 3.0.0 Build id: 200404281424
How to reproduce the problem:
1. Create a simple plug-in project.
2. Start a runtime workbench launch configuration.
3. Open Help->About->Plugin details
The newly created plugin project is not loaded.
Thanks for your help | critical | RESOLVED | WORKSFORME |
{'$oid': '52e9c11254dc1c25ebdc08f9'} | 61,075 | Build 20040428
The implementation relies on not checking array length upfront and rather deal
with exceptions. However, these seem to be quite frequent, and we may either
change our default sizes for arrays, or perform bound checks. | normal | VERIFIED | FIXED |
{'$oid': '52e9c11254dc1c25ebdc08fa'} | 61,082 | The declaration of a sticky view should also specify what side of the window it
should be docked on. | enhancement | CLOSED | FIXED |
{'$oid': '52e9c11354dc1c25ebdc08fb'} | 61,083 | The right-click compile action for Probekit in Hyades today says "Probekit >
Compile" but that's confusing if you have a proprietary extension to Probekit
that uses a different compile action (e.g. a builder). The manual compile
action is really just for the static instrumentation (ProbeInstrumenter) use
case, and will have no effect on users who have a builder.
At least one user (my office-mate) has already been confused by having two ways
to compile probes. If it's not too late for this UI change, I want to change
the text of the right-click action label to "Compile for use with
ProbeInstrumenter" or something. | normal | CLOSED | FIXED |
{'$oid': '52e9c11354dc1c25ebdc08fc'} | 61,084 | The intent was for details to be loaded when required, but currently details are
always loaded by ShrikeCTStubLoaderImplNotForUnits.inferRelationships, which is
called every time the concern model is built. This method calls
ConcernSpaceImpl.getConcerns() which in turns calls
ExtensionalGroupImpl.getElementsTransitive(), which is what causes the details
to be loaded for all units.
This results in the concern model building in the UI taking a long time. Instead
the details loading could be defered until later. From my simple test with the
demo projects, concern model building took less than half the previous time (5s
instead of 13s). We'd need to ensure that operations such as queries that need
full details, cause the details loading to be triggered.
This bug is therefore to look at changing the implementation of
ShrikeCTStubLoaderImplNotForUnits.inferRelationships such that it avoids full
details being loaded.
(Peri, as we don't have the new categories yet, I'll leave it to you to assign
this one as appropriate.) | normal | RESOLVED | FIXED |
{'$oid': '52e9c11354dc1c25ebdc08fd'} | 61,088 | In addition to existing dependency on o.e.core.runtime.compatibility. | normal | CLOSED | FIXED |
{'$oid': '52e9c11354dc1c25ebdc08fe'} | 61,085 | Today's I build (0505), Windows XP
My workspace has all the sdk plugins imported as binaries.
I did a java search for ProgressMonitorDialog within my working set (all the
update plugins) and got a stack overflow:
!SESSION May 05, 2004 12:42:13.887 --------------------------------------------
-
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
!ENTRY org.eclipse.ui 4 4 May 05, 2004 12:42:13.887
!MESSAGE Unhandled event loop exception
!ENTRY org.eclipse.core.resources 2 1 May 05, 2004 12:42:13.887
!MESSAGE Skipping builder org.eclipse.pde.ui.ManifestBuilder for project
org.eclipse.update.tests.core. Either the builder is missing from the install,
or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.ui 4 0 May 05, 2004 12:42:13.897 | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11354dc1c25ebdc08ff'} | 61,086 | This is very reproducible, even with new workspaces. The first I open Eclipse
for on a workspace and click Help -> Help Contents, it opens the help window
just fine. However, when I exit and re-start Eclipse (and each subsequent
time), if I click Help -> Help Contents, Eclipse exits with the following
message:
JVM Terminated. Exit code=1
C:\bea\jdk141_02\bin\javaw.exe -cp E:\eclipse-3.0M8\startup.jar
org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86 -showsplash
E:\eclipse-3.0M8\eclipse.exe -showsplash 600 -exitdata E:\eclipse-3.0M8
\eclipse.exe -exitdata bc0_60 -data s:\tmpws -vm C:\bea\jdk141_02
\bin\javaw.exe -vmargs -cp E:\eclipse-3.0M8\startup.jar
org.eclipse.core.launche.Main
There is no .log file created.
The commandline I use to start Eclipse is:
E:\eclipse-3.0M8\eclipse.exe -vm C:\bea\jdk141_02\bin\javaw.exe -data s:\tmpws
E:\ is a second hard disk and S:\ is a subst'ed drive pointint to E:\views\main
I have also tried this using the latest JDK 1.4.2_04, with the same behavior. | critical | RESOLVED | WORKSFORME |
{'$oid': '52e9c11354dc1c25ebdc0900'} | 61,087 | In an earlier bug I said that I couldn't change the port number that the RAC-
assisted file copy feature used. Now I see that was wrong - there is
a "filePort" setting which can appear in ServiceConfig.xml to override the
default.
However, this is hard for a user (like me) to find. The default
ServiceConfig.xml file created by SetConfig has attributes for the "port"
and "securePort" but nothing for "filePort," so it's impossible for a user to
know how to change it without looking at the RAC source code.
I think SetConfig should write filePort into the default ServiceConfig.xml,
using the default port number, in order to make it obvious how to change this. | normal | CLOSED | FIXED |
{'$oid': '52e9c11354dc1c25ebdc0901'} | 61,090 | The PMC has decided that this should be a preference page rather than a menu
entry | normal | CLOSED | FIXED |
{'$oid': '52e9c11354dc1c25ebdc0902'} | 61,089 | I switched from the Java perspective to the Debug perspective and then back
again. I had twelve editors open and there was only one tab (whose title was
compressed) and the drop down with 11. I would expect more tabs to be visible.
I will attach a screen shot. | normal | RESOLVED | DUPLICATE |
{'$oid': '52e9c11354dc1c25ebdc0903'} | 61,094 | I20040505
This is easy for non local types since we can use fully qualified names.
However for local types additional support is needed from Core since locals
don't have fully qualified names. | normal | RESOLVED | DUPLICATE |
Subsets and Splits