Red Hat Bugzilla – Bug 182711
Doesn't work with Bugzilla v 2.20: no Products found
Last modified: 2007-11-30 17:11:25 EST
Description of problem:
When adding a Bugzilla server that runs version 2.20 or 2.20.1 (and probably
newer versions as well), eclipse-bugzilla is not able to retrieve the products
list from the server.
Version-Release number of selected component (if applicable):
The one available via Eclipse update under http://people.redhat.com/jpound/update
Just add a Bugzilla BugSystem to the View that connects to a Bugzilla server
running version 2.20+. Then try to add a Query and you'll see there are no
Products listed to choose from (and no other components either).
The version available at the update site is an older version. We are currently
in the process of moving update sites and also updating the version that's
there. I'll post on this bug as soon as we do that so that you can updgrade and
Any news here, Igor?
Thanks for the reminder Andrew. There is now a new update-site at
http://sourceware.org/eclipse/update , could you try the version there (0.2.2)
and verify if this still occurs?
(In reply to comment #3)
> Thanks for the reminder Andrew. There is now a new update-site at
> http://sourceware.org/eclipse/update , could you try the version there (0.2.2)
> and verify if this still occurs?
Thanks for the update. I changed my update site reference to the new location
and updated the bugzilla feature. Now I get the following exception, when
opening the "Bug Systems" view (see below). I'm not quite sure whether the
install/update went OK on my machine, as I'm not able to see the Bugzilla
feature in the "Manage Configuration" dialog.
I'll try with a fresh eclipse (3.1.2) installation tomorrow and report back asap!
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
I've seen this error before, it is because of some changes to the persistence
layer (how we store information about bugs you viewed). Unfortunately it's a bit
flaky, it happens sometimes, but not always.
I believe that if you close Eclipse, and then reopen it then this issue should
go away. If it this doesn't help, please try running it with a new workspace and
adding opening the Bugs View. Please let me know how this works. If you cannot
make it work in your old workspace then please let me know here. Reinstalling a
fresh Eclipse is a pretty drastic measure, and I think is unneeded in this case.
Andrew, could you please reassign the bug to me?
FYI I fixed the bug that gave you the NullPointerException, this should be in
the next release.
Could you also verify whether the solution above solved this problem for you?
sorry for the delay, I have been abroad for a couple of days.
I'll test the NullPointerException case tomorrow, when I'm back at the office.
Meanwhile, I tried version 0.2.2 on a fresh (and thus nearly empty) installation
of Bugzilla 2.20.1, on eclipse 3.1.2 (an installation that never saw the
bugzilla plugin before) on Linux (FC3) and can confirm that it works.
I can't see the "Classifications", though, but I assume, this is not (yet?)
supported, being a rather new bugzilla feature.
Thanks for testing, I'm glad it works. I am going to close this bug for now
since the problem is resolved. Please let me know if this returns.
You're right, Classifications are not supported yet. This is most evident with
the eclipse.org bugzilla which is pretty broken without classification ( see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179180). We are working on
this and I hope this will be solved within a week or two, please look at the
website for announcements of a new version.
I made the tests in my other environment at work (Windows, eclipse 3.1.1), using
bugzilla plugin 0.2.2, using a new workspace, as you suggested:
- the view openes now without exception.
- I am able to add a bug system connected to my bugzilla 2.20.1 installation.
- I still don't see any products or other elements, e.g. bug properties in the
"Advanced" mode of the "Add Query" dialog.
- I get error messages when trying to add a bug# (Add > Bug Report... and
Add > Query...).
I'll attach screenshots of the dialog boxes and the relevant parts of my web
server's (apache) access log.
Created attachment 126209 [details]
Error dialog when adding a query
Created attachment 126210 [details]
Error dialog when adding a bug report
Created attachment 126211 [details]
Apache access log file
I investigated things a little further. I had this working on my other
installation, but not on this one, so I suspected some Bugzilla configuration
issue being the cause. And so it was:
The "requirelogin" parameter has to be set to "off" or "no" for this to work.
Although you provide login information input fields in the "Add Bugsystem"
dialog, they seem to address different things. Should this be made an issue of
Thanks for the informative analysis. The bugzilla plugin currently does not
support logging into a bugzilla because it doesn't support any operations that
usually require it (i.e. adding a bug, changing a bug, etc.). Most public
bugzilla installations do not require you to log in in order to view bugs, so
the plugin work.
The fields in the Add Bug System dialog are experimental (and there's a warning
about this), and currently only work with the Red Hat bugzilla (this one). The
reason being that the Red Hat bugzilla has an implementation of an XML-RPC
interface that allows me to easily implement complex operations, for other
bugzillas we need to use screen scraping for that. There is an effort to get
this sort of support into the upstream bugzilla
(https://bugzilla.mozilla.org/show_bug.cgi?id=224577), but it's not there yet.
Is there any particular compelling reason that you need to be able to have
login=on? If it's important I will see how difficult that would be to implement.
(In reply to comment #15)
thanks for your clarification.
I feel, an XML-RPC interface would be an important addition to Bugzilla.
I am using a "bridge" between my version control (subversion) and bugzilla, but
it's rather a kludge, parsing URLs, hacking together HTTP POSTs and so, and very
much bugzilla version dependent...
> Is there any particular compelling reason that you need to be able to have
> login=on? If it's important I will see how difficult that would be to implement.
No reason, at least not now, as we're using bugzilla internally, in a non-routed
subnet only. So I simply changed settings to requirelogin=off and it's OK for now.
Well, thanks a lot for your help!
Glad to help, let me know if you have any other problems.
*** Bug 185723 has been marked as a duplicate of this bug. ***