Bugzilla – Full Text Bug Listing
| Summary: | [connector] CollabNet IssueZilla/IssueTracker | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> | ||||||||||||||||
| Component: | Mylyn | Assignee: | Mylyn Inbox <mylyn-inbox> | ||||||||||||||||
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | |||||||||||||||||
| Severity: | enhancement | ||||||||||||||||||
| Priority: | P4 | CC: | mik.kersten, pombredanne, robert.elves, tfmorris, wes.coelho | ||||||||||||||||
| Version: | 0.3 | Keywords: | helpwanted | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Hardware: | PC | ||||||||||||||||||
| OS: | Windows XP | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Eugene Kuleshov
Eugene: in the Bugzilla preferneces try to set the version to 2.16 since they may be using that. Shawn: if that doesn't resolve it let's make sure to look into it this week. (In reply to comment #1) > Eugene: in the Bugzilla preferneces try to set the version to 2.16 since they > may be using that. > > Shawn: if that doesn't resolve it let's make sure to look into it this week. Doesn't work with 2.16 either. Query fields are still empty. Errors in the log: Failed to execute runnable (java.lang.IllegalArgumentException: ) org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: ) at org.eclipse.swt.SWT.error(SWT.java:2942) at org.eclipse.swt.SWT.error(SWT.java:2865) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3057) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:153) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:303) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:447) at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:261) at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:1066) at org.eclipse.mylar.bugzilla.ui.actions.RefreshBugzillaReportsAction.runWithProgressBar(RefreshBugzillaReportsAction.java:129) at org.eclipse.mylar.bugzilla.ui.actions.RefreshBugzillaReportsAction.run(RefreshBugzillaReportsAction.java:69) at org.eclipse.mylar.bugzilla.ui.actions.RefreshBugzillaReportsAction.run(RefreshBugzillaReportsAction.java:193) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:441) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3080) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2713) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) 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:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948) Caused by: java.lang.IllegalArgumentException: at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:58) at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:42) at org.eclipse.core.runtime.Status.setMessage(Status.java:174) at org.eclipse.core.runtime.Status.<init>(Status.java:81) at org.eclipse.mylar.bugzilla.core.search.BugzillaSearchEngine.search(BugzillaSearchEngine.java:283) at org.eclipse.mylar.bugzilla.ui.tasklist.BugzillaCategorySearchOperation.search(BugzillaCategorySearchOperation.java:93) at org.eclipse.mylar.bugzilla.ui.tasklist.BugzillaCategorySearchOperation.execute(BugzillaCategorySearchOperation.java:71) at org.eclipse.mylar.bugzilla.ui.tasklist.BugzillaQueryCategory.refreshBugs(BugzillaQueryCategory.java:114) at org.eclipse.mylar.bugzilla.ui.actions.RefreshBugzillaReportsAction$2.run(RefreshBugzillaReportsAction.java:168) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:150) at org.eclipse.ui.internal.UISynchronizer$1.run(UISynchronizer.java:36) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) ... 34 more Task details update failed java.lang.NullPointerException at org.eclipse.mylar.bugzilla.ui.tasklist.BugzillaTask.updateTaskDetails(BugzillaTask.java:354) at org.eclipse.mylar.bugzilla.ui.tasklist.BugzillaTask$GetBugReportJob.run(BugzillaTask.java:340) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) The problem here is that Collabnet is a customized version of bugzilla which we are currently unable to support unless we add a new parser for it so that we can properly do the screen scraping. Could you add proper error handling for that, and pop up a dialog saying something like "The Bugzilla version you are using is either not supported, or you need to change the Bugzilla preferences to us the correct version number." The fileds showing up blank is confusing. Also, under "Known Limitations" could you add that customized versions of bugzilla are not supported? We'll have to make sure to closely support anyone interested in extending the Bugzilla client to customized versions. But once you've done the extra error checking we'll have to mark down the priority because we don't have the resources to do it ourselves for 0.3.x. Perhaps the work-around for people using this version is to have them create a "custom query" via HTMl and use the internal browser for viewing reports? I will add a dialog that informs the user that we were unable to get any data from the bugzilla server and it may be becuase there are problems with the server or the server being used is not supported due to being customized. (In reply to comment #5) > We'll have to make sure to closely support anyone interested in extending the > Bugzilla client to customized versions. But once you've done the extra error > checking we'll have to mark down the priority because we don't have the > resources to do it ourselves for 0.3.x. How difficult it is to support a customized bugzilla version? Is there are an infrastructure for this? I guess "bugzilla version" property should be configured per repository. See my summary at http://dev.eclipse.org/mhonarc/lists/mylar-dev/msg00037.html > Perhaps the work-around for people using this version is to have them create a > "custom query" via HTMl and use the internal browser for viewing reports? This is quite usless because you can't create mylar's context for query results. Yup Eugene, this sort of customization support will be a part of the longer-term repository support strategy that you outlined. Fyi I'll answer your message today or tomorrow, still thinking about the best appraoch.. You should definitely be able to create a context for a query hit just by hitting the glasses. Then you'll notice that the big bug icon turns into a little bug over a clipboard, indicating that it's not just a hit anymore, but a report and context stored locally. Please report a new bug if this doesn't work. (In reply to comment #8) > You should definitely be able to create a context for a query hit just by > hitting the glasses. Then you'll notice that the big bug icon turns into a > little bug over a clipboard, indicating that it's not just a hit anymore, but a > report and context stored locally. Please report a new bug if this doesn't work. What I've tried to say is that it won't work on a list of bugs shown in web page as you've suggested for nonstandard repositories. :-) Ah. Yes, that's right, we would need at least the support for gathering query results. But that's a lot simpler then all the suff needed for the bug editor and for the Query UI. Shawn: could you comment on bug #107062 about how hard the custom query thing would be to implement? (In reply to comment #10) > Ah. Yes, that's right, we would need at least the support for gathering query > results. But that's a lot simpler then all the suff needed for the bug editor > and for the Query UI. I believe it would be fine to have custom parser for the results anf everything else in the UI (query editor, bug details, etc.). This was the approach taken by Buglist plugin. > Shawn: could you comment on bug #107062 about how hard the custom query thing > would be to implement? I can try to get some support from Collabnet to help with the parser. That would be fantastic. The only thing we should be careful about is to figure out whether our Bugzilla plug-in should be parsing XML in some places where it currently isn't, in case this helps insulate it from customizations. I guess the first thing to do is to have us try and make the custom query stuff work since it is possible for them to work for CollabNet, and then see what else needs doing. I'm changing the priorities of these two bugs accordingly. We don't have the resources for it right now, but will try to involve CollabNet or other developers to help out. can i help you to develop this parser for CollabNet? i can make it in my thesis, please contact me at: marco.sferra@virgilio.it Marco: contributing CollabNet support would be a very useful contribution, and would help make the current Bugzilla support generic enough to handle customized Bugzilla implementations. Let's start out by discussing what's involved on this report. The main thing will likely be adapting the fragile screen scraping that we do. What would be great is if you could try it with a common CollabNet installation (e.g. the http://subclipse.tigris.org/issues/ Eugene suggests) and Outline what breaks and what the failures are. To start I would ignore making the Bug Editor work, since we can always fall back to the web editor. But what we really do need is query results to be populated. So I suggest starting by adding a new "Custom Query" for Tigris (see top of New Bugzilla Query box) and see what works/fails in getting the query results. Ok, i will begin and i hope to have understood what i have to do...i will send to you what breaks and what the failures are. if you need me you can send everything at marco.sferra@virgilio.it I tried to submit a query in Tigris and it reports to me everything...it doesn't show to me bugs in the editor. now i will tried to see more Good to hear that query results are showing up. What is the failure in the Bug Editor? I would like it to fail softly and fall back on using the Web Browser. If you could paste in the query string that you are using that would be useful too. if you try to see some bug it reports this error java.lang.NullPointerException at org.eclipse.mylar.bugzilla.ui.editor.ExistingBugEditor.getTitleString(ExistingBugEditor.java:307) at org.eclipse.mylar.bugzilla.ui.editor.AbstractBugEditor.createAttributeLayout(AbstractBugEditor.java:521) at org.eclipse.mylar.bugzilla.ui.editor.AbstractBugEditor.createLayouts(AbstractBugEditor.java:509) at org.eclipse.mylar.bugzilla.ui.editor.AbstractBugEditor.createInfoArea(AbstractBugEditor.java:452) at org.eclipse.mylar.bugzilla.ui.editor.AbstractBugEditor.createPartControl(AbstractBugEditor.java:352) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:609) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:384) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:552) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:283) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:126) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:391) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1102) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1051) at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1256) at org.eclipse.ui.internal.PartStack.add(PartStack.java:442) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:109) at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60) at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:212) at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:202) at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:758) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:665) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:628) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2360) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2295) at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage.java:2287) at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2273) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2268) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2241) at org.eclipse.mylar.bugzilla.ui.ViewBugzillaAction.runInUIThread(ViewBugzillaAction.java:72) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:93) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3057) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948) and in query result there is only ONE bug while on the site there are 250 bugs... Marco: is it possible for you to give me a link to the CollabNet repository? What I could do is make the Bug Editor display the report in a web page if it fails to render it. Getting a single query result means that the query parser is not working correctly. The problem will be in the BugzillaSearchEngine.search(..) method, which is failing to match regular expressions. Note how I made it work for Bugzilla 2.20, and you may be able to create a patch that does something similar for CollabNet. That will need to be done in a test-driven way because this messy and old code is very brittle. So I suggest looking at the related Bugzilla tests, writing a new search test that works for a public Bugzilla 2.20 server (e.g. eclipse.org), then adding one for CollabNet and regular expressions for making it pass. Note RegularExpressionMatch test, sine you may want to start with something like that. Let me know how it goes. Here are few repositories based on CollabNet Bugzilla: Subclipse traker at tigris.org http://subclipse.tigris.org/issues/buglist.cgi?Submit+query=Submit+query&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time Some project ad BEA dev2dev https://xcommonj-work.projects.dev2dev.bea.com/issues/buglist.cgi?Submit+query=Submit+query&component=xcommonj-work&subcomponent=www&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&version=current&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Issue+Number Glassfish project at java.net https://glassfish.dev.java.net/issues/buglist.cgi?Submit+query=Submit+query&component=glassfish&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&version=9.0pe&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=glassfish_bugs&newqueryname=&order=Reuse+same+sort+as+last+time ok, i will see to create a method to send a regular expression to collabnet server. thanks eugene i can write regular expression for collabnet but i did't find regular expression library...please post link else i can't try and post my code i have the code but now there are two way to insert this in the class: one is easy but in that class will be very hard change something.. second is very long to do because i have to rewrite a lot of methods, but in the future we can add a lot of regular expression in easy way what do you think? Since the Bugzilla Client has very insufficient test coverage minimizing changes to the code is key. What would be great is if you could put most of the code into a unit test that demonstrates how it works (including parsing from a server), and then we could iterate on generalizing the bugzilla stuff to support additional regular expressions, etc. Would that work? ok, see this test and tell me what do you think. download code from: http://www.kekkko86.altervista.org/file/test.rar That's a great start Marco. The next step is to make this run as a unit test, and to contribute it as a patch by attaching the patch to this report. See instructions on http://eclipse.org/mylar/dev.php on patches. Make the test similar to org.eclipse.mylar.bugzilla.tests.RegularExpressionMatchTest. However, you should make the patch go into org.eclipse.mylar.sandbox/testsrc since it won't be run as a part of the regular test suite. try this and tell me more http://kekkko86.altervista.org/file/Mylar%20Patch.rar The patch needs to be attached to the Bugzilla report in order to make it possible to check into CVS (due licensing details). Could you please add it as an attachment via the "Create a New Attachment" link visible in the web UI? Created attachment 31935 [details]
CollabNet support
what i have to do now? Sorry for the slow reply Marco. Please read comment#27 for what should be created for the patch--this will need to be done in a test-driven way, and should not modify bugzilla.core. You could extend the search engine class if that helps write the test. sorry mik, i did patch for bugzilla.search and i did test for this patch...now i don't understand what i have to change. have you seen my patch? mik, i build a new patch for mylar 4.7. Tell me what do you think about this. Created attachment 33757 [details]
CollabNet support
Marco, this is the comment I thought I had posted to the bug last week but just noticed it didn't go through. Will look at your patch today or tomorrow. --- The patch can not be made to the org.eclipse.mylar.bugzilla.core project because that could break existing support. The patch needs to go in as a test case to org.eclipse.mylar.sandbox. To make this easier I have crated the following class for you: org.eclipse.mylar.sandbox.tests.CollabNetRegularExpressionTest Now, I realize that BugzillaSearchEngine.createHit(..) won't do the right thing for you. So either create your own method in the test case that will, or let me know and I can make BugzillaSearchEngine extensible so that your test case can create a subclass and override createHit(..). Either way all of your changes should be localized to the test case for the time being. Happy hacking :) ok, look this and tell me more :) Created attachment 34145 [details]
collabnet -sandbox
Several problems: - Patches need to be created using the patching mechanism, see http://www.eclipse.org/mylar/doc/contributing.php for more info - Note the above instructions on formatting - Patch didn't compile, but organizing imports and a fixing a variable reference fixed that. Other than that, the patch looks promising and I have committed it. So you should synch up to make sure that you are using the latest one, and base future patches off that. Now the thing to do is to give your testMatchV220 method a more accurate name, and add an assertion for every read method that you have, to ensure that they all behave as expected. Created attachment 34502 [details]
collabnet-sandbox
Mik, i did it. look this and tell me more :D Sorry for the slowness Marco, this has had to get scheduled behind refactorings to the task list to better support multiple repository providers. I plan on looking over your patch tomorrow or next day. Marco, I tried to apply the patch, but the test fails with the following: junit.framework.ComparisonFailure: expected:<nor> but was:<<td class="red"><span class="issue_type">nor</span>> at junit.framework.Assert.assertEquals(Assert.java:81) Also, please generate patches for the project, not just for the file (see http://www.eclipse.org/mylar/doc/devref.php#contributing-patches). Created attachment 35718 [details]
support CollabNet
Marco, this patch is still not created correctly (it's a patch for 2 files, which makes it hard to apply, not for a project). Please re-read the instructions at: http://www.eclipse.org/mylar/doc/devref.php#contributing-patches (and create the patch by right-clicking the project or change set). Created attachment 36052 [details]
collab support
sorry mik for this loss of time and my errors
We've had our hands full with 0.4.10 and EclipseCon, will plan to review this next week. Created attachment 36551 [details]
CollabNET support
Marco: it is now looking promising for the solution discussed on bug 136219 to provide a robust solution to this. Before continuing further on making the HTML parsing work for CollabNet we need to investigate that in case it removes the need for HTML parsing entirely. Will keep you posted on this and the corresponding report. Mylar 0.5.2, released today, no longer relies on HTML parsing and interoperates with customized repositories such as RedHat. As such CollabNet integration should be considerably easier. Rob, you did a bit of exploration here, what did you learn? (In reply to comment #50) > Mylar 0.5.2, released today, no longer relies on HTML parsing and interoperates > with customized repositories such as RedHat. As such CollabNet integration > should be considerably easier. I guess it will still require something for detecting and handling base repository url, since it could be moved around quite a bit... Looking at http://subclipse.tigris.org/issues/ , I couldn't get access to reports in xml format (ctype=xml) nor could I get to a config.cgi. Both of these are required for the bugzilla connector to work. (In reply to comment #52) > Looking at http://subclipse.tigris.org/issues/ , I couldn't get access to > reports in xml format (ctype=xml) nor could I get to a config.cgi. Both of > these are required for the bugzilla connector to work. Try this: http://subclipse.tigris.org/issues/xml.cgi?output_configured=true&id=103:117:131:135:215:268:306:321:351:378:385:386:394:397:401:412:414:418:421:422:423:437:440:442:449:450:456:463:464:469:471:472:473:474:476:479:481:482:484:485:491:493:494:495:496:497&include_attachments=true&download_type=browser Apparently you need to get list of id's from somewhere. Not sure how to get that list other then html. I can try to ask CollabNet folks... Perfect, this will get us bug reports, now we just need the configuration (products, milestones, components, status values, etc as rdf), oh and can we get query results in rdf (I guess this would be the list of ids you mentioned)? Required data from Collabnet: 1) Query results in RDF format. Example: https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylar&component=Bugzilla&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&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=&ctype=rdf Note: We also use the query facility to reduce the amount of synchronizing by querying for reports that have changed since a given date/time (accurate to second). 2) Issues/reports in XML format. Example: https://bugs.eclipse.org/bugs/show_bug.cgi?id=106990&ctype=xml Content needs to include issue attributes, comments, and attachments. 3) Repository configuration in RDF. Example: https://bugs.eclipse.org/bugs/config.cgi?ctype=rdf Products, components, valid status values, mappings between products, components, and target milestones, etc. Note that this link may display an error in your browser. The source is okay but we have been forced to clean it up ourselves. Ideally the product and component names etc would be properly escaped so as to avoid this problem. (In reply to comment #55) Rob, this is for ideal situation. However I believe that there should be some support for existing installations. > Required data from Collabnet: > > 1) Query results in RDF format. Example: > https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylar&component=Bugzilla&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailtype1=substring&email1=&emailtype2=substring&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=&ctype=rdf > > Note: We also use the query facility to reduce the amount of synchronizing by > querying for reports that have changed since a given date/time (accurate to > second). As I suggested before you can get list of id's with minimum html parsing even for queries with date/time. Then second query can be used to retrieve all details for those id's. Besides, it sounds like repository-specific optimization and may not be generally avaialable on XYZ repository provider. > 2) Issues/reports in XML format. Example: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=106990&ctype=xml > Content needs to include issue attributes, comments, and attachments. http://subclipse.tigris.org/issues/xml.cgi?id=497 Attachments are encoded in base64. > 3) Repository configuration in RDF. Example: > https://bugs.eclipse.org/bugs/config.cgi?ctype=rdf > > Products, components, valid status values, mappings between products, > components, and target milestones, etc. > > Note that this link may display an error in your browser. The source is okay > but we have been forced to clean it up ourselves. Ideally the product and > component names etc would be properly escaped so as to avoid this problem. This one is still unclear know how to get. As a fall back, maybe it can be just manually configured in repository provider preferences with some defaults. Free Mylyn connector for CollabNet IssueZilla/IssueTracker is available from http://eclipse.open.collab.net/ |