[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [p2-dev] undeclared exception being thrown in 3.4.1
|
Thanks,
That has been changed in 3.5 - the transport classes are rewritten,
and the corresponding method on RepositoryTransport takes a monitor as
an argument.
Henrik Lindberg
henrik.lindberg@xxxxxxxxxxxxxx
On Apr 20, 2009, at 6:03 PM, Haigermoser, Helmut wrote:
addendum:
ECFMetadataTransport.getLastModified(ECFMetadataTransport.java:143)
does
not have a progress monitor argument...
-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
On
Behalf Of Haigermoser, Helmut
Sent: Monday, April 20, 2009 5:58 PM
To: P2 developer discussions
Subject: RE: [p2-dev] undeclared exception being thrown in 3.4.1
Ciao John :)
I still don't see the reason for throwing an undeclared exception but
this is starting to look like a general eclipse problem, not a p2/ecf
bug we are running into now. The assumption that's being made by the
person throwing the exception is that everybody watches and catches
OperationCanceledExceptions, an assumption that can't currently be
supported by JDT features...
My suggestion would be to avoid throwing an undeclared exception, or ,
as a convenience, add support to JDT allowing us to see such potential
application killers before they ship to the customer. If what you
say is
true and any method taking in a monitor needs to be checked for
OperationCanceled then this could be implemented fairly easily, though
the nice way would be to use IStatus or notify the UI some other way,
via an event bus or whatever... :) HTH, Ciao, hh
