From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
There are various places in Eclipse where it accesses a network e.g. for CVS access, or in the Bugzilla plugin.
If the user is on a laptop with intermittent network connectivity, Eclipse should spot that you don't have a network connection before any kind of automatic refreshing.
NetworkManager provides a convenient API for deciding whether we have a network connection within GNOME: http://people.redhat.com/dcbw/NetworkManager/
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up Eclipse on a laptop
2. Checkout a project from CVS
3. shutdown Eclipse,
4. go somewhere without network access
5. start up Eclipse
Actual Results: Not sure, but overholt believes it delays your startup until the attempt to contact CVS times out.
Haven't actually tested yet though.
Expected Results: Should figure out it hasn't got network connectivity and give up immediately.
(Exactly how this would be implemented on different platforms is also an interesting question; also note that NetworkManager isn't on by default on Fedora)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I think it is Java responsibility to fail connection if there is none...
The bug is about not trying to make a connection at all. Like the offline mode in Firefox.
Not doable in predictable future.
Eclipse relies on java and afaik does not have centralized place through which all network traffic is routed.
If there are any specific places, which should be improved, we need separate and specific upstream bugs opened against appropriate upstream components.