[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] ProvisioningPlan.getRequestStatus()

Hi Thomas,

That method mainly isn't on the interface because nobody was calling it outside of the tests. I was trying to trim down the API as much as possible. In this particular case, I'm not sure why we have both getStatus() and getRequestStatus(). It seems to be there only needs to be a single global status that gives a high level summary of the planning result. Simon and I were planning to do another iteration on this API soon so we can take a closer look and see if two status are really needed, or if there is some way we can fold them together.


Thomas Hallgren <thomas@xxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx

12/02/2009 10:58 AM

Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

P2 developer discussions <p2-dev@xxxxxxxxxxx>
[p2-dev] ProvisioningPlan.getRequestStatus()

The Buckminster Aggregator uses the global request status returned by
ProvisioningPlan.getRequestStatus() to figure out what went wrong in
case of trouble. In the new API, this method is not represented in the
IProvisioningPlan interface. There's only a method that takes an IU as
an argument, and well, I don't know what IU that caused the problem.
That's what I want to find out. My objective is to examine the problem
and send a relevant email to whoever contributed the failing IU to the
aggregation. In order to do that, I think I need the global request status.

Is the lack of this method an oversight or should the problem be
attacked differently?

Thomas Hallgren

p2-dev mailing list