[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [mylar-dev] netbeans Tasklist module
|
Rob and I (I assume you meant Rob and not Brock) have to focus on the core
tasklist and context support to make it easier for others to build
connectors. Which is why the bug below is still in "helpwanted" land. What
we need for any kind of reasonable integration is the IssueZilla folks to
provide XML/RDF output for bugs, as discussed on the on the report. It's
unfortunate that they forked at 2.13 in a way that precluded merging back.
But it shouldn't be that hard for them to implement it...
106990: [connector] CollabNet IssueZilla/IssueTracker
https://bugs.eclipse.org/bugs/show_bug.cgi?id=106990
Mik
> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Monday, June 19, 2006 9:50 AM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] netbeans Tasklist module
>
>
> Sure, though I don't really feel fancy about retrieving all the issue
> details from html pages. Would be easier to get the titles from
> individual issue pages, though it would be much slower.
>
> Anyways, what about IssueZilla support? Do you and Brock have
> resources/time to handle it? At least some basic functionality without
> form-based editor and offline...
>
> regards,
> Eugene
>
>
> Mik Kersten wrote:
> > Hmmm, I wonder if your generic web repository provider could take a
> regexp
> > to find bug URLs from a query? We have all the HTML parsing code from
> back
> > when Bugzilla used to do it.
> >
> > Mik
> >
> >
> >> -----Original Message-----
> >> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx]
> >> On Behalf Of Eugene Kuleshov
> >> Sent: Sunday, June 18, 2006 8:20 PM
> >> To: Mylar developer discussions
> >> Subject: Re: [mylar-dev] netbeans Tasklist module
> >>
> >>
> >> No way these can be used directly. No unit tests, AWT and org.openide
> >> classes are used all over the place. Though one could rip them off and
> >> use that code to implement Mylar providers. IssueZilla and Scarab has
> >> been requested for some time.
> >>
> >> Anyways, I checked implementation of IssuzeZilla (java.net and
> >> netbeans.org) and apparently they are using approach similar to what
> >> I've suggested - run query, search for magic string "show_bug.cgi?id="
> >> and then run another request to get all issue details using
> >> "xml.cgi?id=" with "&show_attachments=false".
> >>
> >> regards,
> >> Eugene
> >>
> >>
> >> Mik Kersten wrote:
> >>
> >>> Check this out: http://tasklist.netbeans.org/
> >>>
> >>> While I didn't see any screenshots of it, it's interesting that they
> >>>
> >> support
> >>
> >>> Issuezilla and java.net. I wonder if they wrote custom screen
> scrapers
> >>>
> >> or
> >>
> >>> came up with a more clever approach that we could use.
> >>>
> >>> I emailed the module owner asking about that, and also suggested that
> >>>
> >> they
> >>
> >>> consider using our bugzilla.core.
> >>>
> >>> Mik
> >>>
> >>>
> >> _______________________________________________
> >> mylar-dev mailing list
> >> mylar-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/mylar-dev
> >>
> >
> > _______________________________________________
> > mylar-dev mailing list
> > mylar-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> >
>
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev
