p2 bugs search [message #128010] |
Fri, 27 March 2009 14:34 |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
With so many p2 bugs open and being addressed for 3.5, I'm having a
problem finding specific things that I want to either report or monitor
the progress of.
One specific example: is there a bug that is tracking the problem in 3.4
where install will just hang (and not even respond to Cancel) if a
mirror is too slow or hangs? As a plug-in vendor, we are often testing
installs of our stuff into 3.4 and this happens several times per week.
It is a huge time killer for us, so I'd like to make sure it is being
addressed for 3.5 and monitor the progress.
Does anyone know of a bug tracking that?
Thanks,
Eric
|
|
|
|
|
Re: p2 bugs search [message #128091 is a reply to message #128040] |
Mon, 30 March 2009 13:48 |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 3/28/2009 11:10 PM, Ben Vitale wrote:
> Eric Rizzo wrote:
>> With so many p2 bugs open and being addressed for 3.5, I'm having a
>> problem finding specific things that I want to either report or
>> monitor the progress of.
>> One specific example: is there a bug that is tracking the problem in
>> 3.4 where install will just hang (and not even respond to Cancel) if a
>> mirror is too slow or hangs? As a plug-in vendor, we are often testing
>> installs of our stuff into 3.4 and this happens several times per
>> week. It is a huge time killer for us, so I'd like to make sure it is
>> being addressed for 3.5 and monitor the progress.
>> Does anyone know of a bug tracking that?
>>
>> Thanks,
>> Eric
>
> This might be the bug you are looking for:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=263613
Yeah, that looks relevant (if I am filtering all of the implementation
discussion correctly - sheesh!).
Thanks,
Eric
|
|
|
|
Re: p2 bugs search [message #128450 is a reply to message #128091] |
Thu, 02 April 2009 20:39 |
Eclipse User |
|
|
|
Originally posted by: eclipseng.arthorne.com
Eric Rizzo wrote:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=263613
>
> Yeah, that looks relevant (if I am filtering all of the implementation
> discussion correctly - sheesh!).
The network responsiveness was greatly improved in 3.5 by switching to
Apache HTTP client rather than the JRE's built in HTTP client. There
have been several other significant fixes in this area in 3.5 (including
the bug above). I think you will find the situation greatly improved in
3.5 builds. Your best bet though is to grab the latest 3.5 milestone and
try it out. If you are hitting problems regularly, it could be related
to your particular servers, your local proxy setup, etc. It's hard to
know for sure if *your* problem is fixed unless you try out a recent
milestone.
--
|
|
|
Powered by
FUDForum. Page generated in 0.03630 seconds