Re: [p2-dev] Interfaces for metadata classes

[Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>]

as I recall, we made it a separate issue since we had several large patches awaiting integration (interfaces, versions, etc.) and wanted to get everything merged before moving the classes.
"Ian Bull" <irbull@xxxxxxxxxxxxxxxxx>

"Ian Bull" <irbull@xxxxxxxxxxxxxxxxx> Sent by: p2-dev-bounces@xxxxxxxxxxx 01/06/2009 08:40 AM Please respond to P2 developer discussions

To: "P2 developer discussions" <p2-dev@xxxxxxxxxxx> cc: Subject: Re: [p2-dev] Interfaces for metadata classes

We decided to make this a separate issue, (so option number 2 in your list :) ).  I will file a bug for this, and put a patch together.

Thanks John

Cheers,
Ian

On Tue, Jan 6, 2009 at 6:20 AM, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:

I noticed that the concrete metadata classes that we created interfaces for are still in the provisional API package. Since we have interfaces to form the API spec, and a factory method for creating instances, the concrete classes can now be moved into internal packages. In fact if we don't, a client could reasonably downcast to the concrete API class, which would break with a different implementation. Was this an oversight, or just staging the changes to make sure we fixed up all references before moving the classes? I vaguely remember a dicussion about this but couldn't see anything in the bug report about it.

John
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

-- 
R. Ian Bull, PhD
Software Developer, EclipseSource
http://www.ianbull.com
http://blog.ianbull.com_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev