Hi, everybody...
Creeping ever so slowly forward I now get back the following output from the sample:
Aug 12, 2008 4:29:05 PM org.apache.commons.httpclient.HttpMethodDirector authenticateHost
WARNING: Required credentials not available for BASIC <any realm>@
landfill.bugzilla.org:443Aug 12, 2008 4:29:05 PM org.apache.commons.httpclient.HttpMethodDirector authenticateHost
WARNING: Preemptive authentication requested but no default credentials available
This is a fancier summary string.
P5
accepting this bug, however turning down the temperature may result in global
cooling...
enhancement
org.eclipse.core.runtime.CoreException: You have to specify a new comment when making this change. Please comment on the reason for this change.
at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.parseHtmlError(BugzillaClient.java:1198)
at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.postTaskData(BugzillaClient.java:858)
at org.eclipse.mylyn.internal.bugzilla.core.BugzillaTaskDataHandler.postTaskData(BugzillaTaskDataHandler.java:251)
at org.eclipse.mylyn.internal.examples.bugzilla.Main.main(Main.java:68)
End of main...
Seeing the descriptive string in the CoreException's cause message my first reaction was to try to set a new comment when making the change... I tried the following (this is admittedly based on pattern matching the rest of the example, and my understanding of the Mylyn APIs is far from solid at this point):
// TaskAttribute commentAttribute = taskData.getRoot().getAttribute(BugzillaAttribute.NEW_COMMENT.getKey());
// System.out.println(commentAttribute.getValue());
// commentAttribute.setValue("In a gada da comment...");
Which gives me:
Aug 12, 2008 4:32:38 PM org.apache.commons.httpclient.HttpMethodDirector authenticateHost
WARNING: Preemptive authentication requested but no default credentials available
This is a fancier summary string.
P5
accepting this bug, however turning down the temperature may result in global
cooling...
enhancement
org.eclipse.core.runtime.CoreException: A repository error has occurred.
at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.parseHtmlError(BugzillaClient.java:1231)
at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.postTaskData(BugzillaClient.java:858)
at org.eclipse.mylyn.internal.bugzilla.core.BugzillaTaskDataHandler.postTaskData(BugzillaTaskDataHandler.java:251)
at org.eclipse.mylyn.internal.examples.bugzilla.Main.main(Main.java:68)
End of main...
Is there something especially rotten about how I tried to create the new comment? When one gets back the "repository error has occurred" message, what's the usual next best step for troubleshooting?
Thanks again for your patience and helpfulness...
Best regards,
Jerry
On Mon, Aug 11, 2008 at 6:52 PM, Steffen Pingel
<steffenp@xxxxxx> wrote:
Sorry about that. It had slipped my mind that this bug was still unresolved
and prevented the example from running.
> Is there an obvious workaround for the problem that I'd know if I was more
> familiar with the mylyn architecture that will get me running with the
> bugzilla connector, or is this a fatal problem for which I have to wait for
> a fix? I'm totally happy to instantiate
>
> BugzillaCorePlugin
>
> or any other reasonable pre-requisite classes to get myself working...
> I'd just need to know what they are and how to do it... :-)
You would also have to invoke start() which might get tricky as it expect a
valid BundleContext. I have posted a patch to bug 242983 that fixes the NPE
in the Bugzilla connector. If you update your workspace and apply that patch
you should be able to run the example.
Please comment on the bug in case you run into other problems when running the
Bugzilla connector as a standalone application.
