Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Interfaces for metadata classes

Friday sounds fine if the version changes have happened.
We also want to see what is going to happen on the resolver front.
After all this sounds relatively secondary and trivial to do that I don't see the need to rush it

Inactive hide details for "Ian Bull" ---01/13/2009 02:46:15 PM---I have opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=26"Ian Bull" ---01/13/2009 02:46:15 PM---I have opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=260913 to track this issue.


From:

"Ian Bull" <irbull@xxxxxxxxxxxxxxxxx>

To:

"P2 developer discussions" <p2-dev@xxxxxxxxxxx>

Date:

01/13/2009 02:46 PM

Subject:

Re: [p2-dev] Interfaces for metadata classes




I have opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=260913 to track this issue.

Does anybody have a preference for when we should do this (i.e. Friday at 4:30 PST) or something?

Cheers,
Ian

On Tue, Jan 6, 2009 at 8:58 AM, Susan Franklin McCourt <susan_franklin@xxxxxxxxxx> wrote:
    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.
    Inactive hide details for "Ian Bull" <irbull@xxxxxxxxxxxxxxxxx>"Ian Bull" <irbull@xxxxxxxxxxxxxxxxx>




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

    _______________________________________________
    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


GIF image

GIF image

GIF image

GIF image


Back to the top