RE: Issuezilla VS. bugzilla

On Wed, 2002-12-18 at 15:23, Andrew Serff wrote:
> Ok I lied, I'm taking a rough stab at it right now.  How does it know

I hope you're not betraying LOTR to play with the tasklist!!

> which BugEngine to grab?  Do I need to change something so it knows
> about the new bugzilla stuff?  

Unfortunately, this is one of the rough areas that need work (as
outlined in one of the bug reports I sent to you).

Ideally, there should be a "New Query" dialog which gives you
a dialog with a combo box where you choose which engine to
use (issuezilla, bugzilla, bugtraq, ...) and based on your
selection, shows a customizer. For issuezilla, it might give
you something similar to the bug query page on netbeans.org,
or perhaps something simpler.

Once you've created a query, it opens up a new view with that
query, using the given engine.  

There are a few pieces missing to do this:
* A way for modules to register additional bug engines. That's
  pretty easy; we can use lookup.
* The bug engine interface should allow one to specify a query
  customizer
* The Issuezilla engine needs to get a customizer
* Queries should get persisted and restored along with the
  bug view. And you should be able to edit the query too.


FOR NOW, to get started, simply go to the evil lines in
BugList.java which does this:

    /** Creates a new instance of TaskList */
    public BugList() {
        IZBugEngine issuezilla = new IZBugEngine(this);
        // Later, allow these puppies to be registered via Lookup
        engines = new BugEngine[] { issuezilla };
    }

and add your own engine; then modify the getDefaultEngine()
method to return yours instead of engines[0].

-- Tor

> 
> Other wise, I think I have made all the changes to the issuezilla code,
> just need to know how to use it.  :)
> 
> Andrew
> 
> -----Original Message-----
> From: Andrew Serff [mailto:[email protected]] 
> Sent: Wednesday, December 18, 2002 4:01 PM
> To: [email protected]
> Subject: RE: Issuezilla VS. bugzilla
> 
> Ya, I just looked too and a lot of the fields are similar.  So I can
> probably just make a new package and copy all the issuezilla stuff over
> and change the names and it might work.  I'll try it this weekend
> hopefully.  Can't tonight...Lord of the Rings is tonight!!  :)
> 
> Thanks for you help
> 
> Andrew
> 
> -----Original Message-----
> From: Trond Norbye [mailto:[email protected]] 
> Sent: Wednesday, December 18, 2002 3:45 PM
> To: [email protected]
> Subject: Re: Issuezilla VS. bugzilla
> 
> 
> Tor Norbye said:
> > On Wed, 2002-12-18 at 13:59, Andrew Serff wrote:
> >> Is Issuezilla that different from Bugzilla that the code to view the
> >> bug database will not work?  If it isn't, how do I make it work.  If
> >> it is, I'd be willing to take a look at how to make it work with
> >> bugzilla (since issuezilla is dead from what I understand).
> >
> > I honestly don't know - I've never used bugzilla.
> >
> > But I believe issuezilla is based on bugzilla so I think they
> > are compatible.
> >
> > Note that the bug module is less mature than the other modules
> > (that's why it has a lower version number).
> >
> > If bugzilla has an XML output option (issuezilla uses xml.cgi?id=") it
> > will probably work, but note that the buglist module may
> > have some hardcoded netbeans.org stuff.
> >
> 
> I just had a look at bugzilla's database, and yes, they have the xml.cgi
> (and the output tags looked similar to what I found in
> IssuzillaXMLHandler....)
> 
>  ;)
> 
> Good luck...
> 
> Trond
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
-- 
Tor Norbye <[email protected]>
Sun Microsystems, Inc