[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Question about RFP44

More generally, I fully expect many of the items in RFP44 to be worked in the Equinox project as these items are, in some cases evolved directly out of Equinox/Eclipse requirements.  The Equinox work is being done with the explicit intent of contributing it directly to the RFCs spun out of RFP44.  


Pascal Rapicault/Ottawa/IBM@IBMCA
Sent by: equinox-dev-admin@xxxxxxxxxxx

08/08/2003 12:57 PM

        To:        pkriens <Peter.Kriens@xxxxxxxx>
        cc:        equinox-dev@xxxxxxxxxxx
        Subject:        Re: [equinox-dev] Question about RFP44


There is no problem in reusing the content of this bug or of any other since the content of this falls under the CPL.


Peter Kriens <Peter.Kriens@xxxxxxxx>
Sent by: equinox-dev-admin@xxxxxxxxxxx

08/08/2003 11:36 AM
Please respond to pkriens

       To:        Pascal Rapicault/Ottawa/IBM@IBMCA

       cc:        equinox-dev@xxxxxxxxxxx

       Subject:        Re: [equinox-dev] Question about RFP44

RFP 44 is a document requesting new functionality, it should not
mention design choices yet. Some of the issues were discussed on the
CPEG meeting yesterday in Munchen, especially the Set return type.

When the RFP is accepted (it looks like it will be because there is no
resistance) then we will write the RFC that lays out the actual
design. The fact that we are considering scopes and fragments
significantly changes our view of the world from a simple jar file to
a collection of jar files. Obviously it will take some effort to
oversee all the implications.

The points you raise are valid and should be captured in the RFC
discussion, can we copy these?

Thanks, kind regards,

      Peter Kriens

PR> I have a question relative to the RFP 44 and the enumeration of resources.
PR> Please see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=41229

PR>         PaScaL

Peter Kriens                              Mob. +46705950899

equinox-dev mailing list