Community
Participate
Working Groups
After adding eclipse bugzilla to the task repositories, I chose properties of this reposiries (context menu). This creates the following exception. Mac OS X 10.4.4, Mylar 0.4.7 on Eclipse 3.2M4 !STACK 0 java.lang.StringIndexOutOfBoundsException: String index out of range: 8 at java.lang.String.getChars(String.java:721) at org.eclipse.swt.widgets.Text.getEditText(Text.java:1062) at org.eclipse.swt.widgets.Text.getText(Text.java:1008) at org.eclipse.jface.preference.StringFieldEditor.checkState(StringFieldEditor.java:185) at org.eclipse.jface.preference.StringFieldEditor.refreshValidState(StringFieldEditor.java:395) at org.eclipse.mylar.tasklist.ui.wizards.RepositorySettingsPage$RepositoryStringFieldEditor.refreshValidState(RepositorySettingsPage.java:139) at org.eclipse.jface.preference.StringFieldEditor.valueChanged(StringFieldEditor.java:495) at org.eclipse.jface.preference.StringFieldEditor.setStringValue(StringFieldEditor.java:439) at org.eclipse.mylar.tasklist.ui.wizards.RepositorySettingsPage.createControl(RepositorySettingsPage.java:84) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:179) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:611) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:502) at org.eclipse.jface.window.Window.create(Window.java:417) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1051) at org.eclipse.mylar.tasklist.repositories.ui.TaskRepositoryPropertiesAction.run(TaskRepositoryPropertiesAction.java:54) at org.eclipse.jface.action.Action.runWithEvent(Action.java:492) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:530) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:480) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:392) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1446) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1455) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1232) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3243) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2894) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1762) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1726) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:397) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:106) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:109) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) 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:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:338) at org.eclipse.core.launcher.Main.basicRun(Main.java:282) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
*** Bug 121318 has been marked as a duplicate of this bug. ***
'Add existing Bugzilla Report' works now, despite this exception. So it's no showstopper any more.
Great. I think I know how to fix it, will post later today.
I just tried this with an OS X box and did not see any problems when using Mylar 0.4.7 (added account and set password with no exceptions). However, I've made this code fail gracefully so you should not see any more exceptions, although an info will be put into the log if a similar failure occurs. If you're seeing those messages or any strange behavior in 0.4.8 feel free to reopen.
