Bugzilla – Full Text Bug Listing
| Summary: | convert bug parser to use xml and rdf sources | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Robert Elves <robert.elves> |
| Component: | Mylyn | Assignee: | Robert Elves <robert.elves> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | ekuleshov, mik.kersten, robert.elves |
| Version: | unspecified | ||
| Target Milestone: | 0.6 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Attachments: | |||
|
Description
Robert Elves
Interestingly, BugZilla integrated into CollabNet has similar feature, though URL is different: https://xcommonj-work.projects.dev2dev.bea.com/issues/xml.cgi?id=1 Yup, this stands a chance of giving us 'free' CollabNet integration (!). I'm very happy that Rob and I sat in on the Bugzilla devs meeting yesterday since that helped point us in the right direction to taking baby steps towards a WS API. Rob: what about getting back query results? There are some difference in tag names for task info, but generally CollabNet does have xml representation for query hits. I didn't noticed it before, but it seems that Bugzilla version on eclipse.org has support for atom feed. E.g.: https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=eu%40md.pp.ru&emailtype1=exact&emailassigned_to1=1&emailreporter1=1&remaction=&query_format=advanced&ctype=atom BTW, there is also a CVS format avialable on both BugZilla and CollabNet. Interesting that issue descriptions are not truncated up there as opposed to html query result page... I'd like to suggest Rome as an rss/rdf/atom parser. So, it could be also used for raw RSS integration. See https://rome.dev.java.net/ Note: There is an open Bugzilla report ( https://bugzilla.mozilla.org/show_bug.cgi?id=264785 ) related to the issue of special characters not being escaped in the RDF/XML export facility. Created attachment 39378 [details]
Progress: Bugzilla server configuration retrieved from rdf.
Created attachment 39381 [details]
mylar/context/xml
rdf configuration context
Created attachment 39429 [details]
Progress: Missing components patch.
Patch applied and verified via adding new query to clean workspace. Rob, you can do the bug stuff on this report, but create a new one for the RDF-based search. When trying to add a new bug report I get the following error after selecting a product: java.lang.NullPointerException at org.eclipse.mylar.internal.bugzilla.ui.wizard.AbstractBugzillaWizardPage.setPlatformOptions(AbstractBugzillaWizardPage.java:742) at org.eclipse.mylar.internal.bugzilla.ui.wizard.AbstractBugzillaWizardPage.createControl(AbstractBugzillaWizardPage.java:382) at It's no longer possible to submit bugs. This error gets logged, and Eclipse has to be killed: java.lang.NullPointerException at org.eclipse.mylar.internal.bugzilla.ui.wizard.AbstractBugzillaWizardPage.setPlatformOptions(AbstractBugzillaWizardPage.java:742) at org.eclipse.mylar.internal.bugzilla.ui.wizard.AbstractBugzillaWizardPage.createControl(AbstractBugzillaWizardPage.java:382) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1046) at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1038) at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.java:1028) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1026) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:757) Created attachment 39484 [details]
Fix npe in AbstractBugzillaWizardPage
Not completely sure how this came about. Here is a patch that will check for the npe. Apply the patch then update your products and try again.
But are you able to submit bugs successfully? I don't think it was just the NPE preventing that. Also, just checking for the NPE will fail to set the platform opions correctly, so that can't be right. You are right. Please ignore the previous patch. New one to follow... I'm also seeing these scary messages printed to my console now and then, and think they might be coming from the Bugzilla support since I saw them way back. Watch for your runtime workspace generating them. [Fatal Error] :-1:-1: Premature end of file. Created attachment 39498 [details]
Progress: fixes new bug submission errors
I did manual tests on 2.20.1 and 2.22. Let me know if you still have problems with eclipse.org.
Patch applied and verified (new bug submitted succesfully to eclipse.org). Problems (hopefully easy to fix): - Instead of the default values being selected for attributes, the top values are now selected. This is bad for us because every bug will be submitted as a P1 "blocker" ;) Need to restore default values. If this is not exposed via config.cgi, you may be forced to select the middle value for priority and severity, and the last value for version, and the top value for component. - OS and Platform selection is not working anymore. Probably because it's matching the wrong strings? Created attachment 39599 [details]
Provides default new bug attributes and OS/Platform detection fixed.
Due to the inconsistent state of my working environment I need you to run all tests, apply the patch, and run them again. Thanks.
Created attachment 39615 [details]
Missed file with error handler.
Patches applied. Created attachment 39833 [details]
More cleaning up of attribute handling
Created attachment 39835 [details]
mylar/context/xml/zip
context for attributes
Strange, but I don't see any attached context for this report. Using Mylar 0.5.1 We changed the "Attachment" description to mylar/context/zip, and this only has the old descriptions (e.g. mylar/context/xml/zip). Btw, I'm about to go offline until Wed. (In reply to comment #26) > We changed the "Attachment" description to mylar/context/zip, and this only has > the old descriptions (e.g. mylar/context/xml/zip). which report has new ones? > Btw, I'm about to go offline until Wed. too bad. :-( (In reply to comment #26) > We changed the "Attachment" description to mylar/context/zip, and this only has > the old descriptions (e.g. mylar/context/xml/zip). Actually, shouldn't be both descriptions supported? The first was just for testing. Here is a query that will return reports with context: https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylar&long_desc_type=allwordssubstr&long_desc=mylar%2Fcontext%2Fzip&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=notregexp&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= (In reply to comment #29) > The first was just for testing. Here is a query that will return reports with > context: > https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylar&long_desc_type=allwordssubstr&long_desc=mylar%2Fcontext%2Fzip&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=notregexp&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= He he. I already got the same one. :-) BTW, see Bug 139404: Add special keyword to issue when attaching contexts https://bugs.eclipse.org/bugs/show_bug.cgi?id=139404 PS: I wonder if Ctrl-C should prepend "Bug " for bugzilla, so it will be hyperlinked when pasted into comments... Created attachment 40093 [details]
mylar/context/zip
RDF Configuration retrieval
Regarding the PS, a slicker way of doing that would probably be to make the Bugzilla editor's "paste" be smarter about pasting a refernce to the report and only paste "bug 123" since that follows the hyperlink policy. Please submit a new bug for that. Created attachment 40670 [details]
Bug reports read from xml stream
Created attachment 40671 [details]
mylar/context/zip
BugReports (BugzillaReport) parsed from xml
Line wrapping needs to be added back. Perhaps now it can be dynamic (i.e. scaled to window width)? Rob, this is working great, we just need to fix up the extra spacing in the editor. Fixed. See bug# 142084 for discussion regarding bugzilla comment layout. |