| Re: [equinox-dev] Equinox->Bundles component is getting crowded |
It would probably be best if each separately downloadable item had its own component against which people could file bugs. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargrave@xxxxxxxxxx office: +1 386 848 1781 mobile: +1 386 848 3788 From: Thomas Watson/Austin/IBM@IBMUS To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx> Date: 2007-09-12 12:34 Subject: Re: [equinox-dev] Equinox->Bundles component is getting crowded For the security stuff I was referring to the security-specific bundles like login (JAAS integration etc.) You are right there is a lot of cross-cutting concerns with the other security related work that will not really fit into any one component. Tom John Arthorne ---09/12/2007 11:25:42 AM---Creating a new component for p2 definitely makes sense to me. I don't know much about the security work, but that may be diffi John Arthorne <John_Arthorne@xxxxxxxxxx> Sent by: equinox-dev-bounces@xxxxxxxxxxx 09/12/2007 11:21 AM Please respond to Equinox development mailing list <equinox-dev@xxxxxxxxxxx> To Equinox development mailing list <equinox-dev@xxxxxxxxxxx> cc Subject Re: [equinox-dev] Equinox->Bundles component is getting crowded Creating a new component for p2 definitely makes sense to me. I don't know much about the security work, but that may be difficult to partition into its own component because it's an inherently cross-cutting concern. If there end up being a number of security-specific bundles, it may make sense. Generally speaking, I think more components is a good thing. It's a great way to bring in new committers who may not be able to make the large commitment needed to contribute across a large part of Equinox. John Thomas Watson <tjwatson@xxxxxxxxxx> Sent by: equinox-dev-bounces@xxxxxxxxxxx 09/12/2007 11:42 AM Please respond to Equinox development mailing list <equinox-dev@xxxxxxxxxxx> To equinox-dev@xxxxxxxxxxx cc Subject [equinox-dev] Equinox->Bundles component is getting crowded The Equinox project continues to grow with new components and new contributes being added. Thanks everyone!! As new contributions are graduated into Equinox proper we need to place them under one of the existing components. Currently we have the "Framework" and "Bundles" components for Equinox proper in bugzilla/cvs. A large majority of the new contributions will fall into the "Bundles" component. For example, we have a few work areas in the equinox incubator which are very active (e.g. p2, security etc). Once this work graduates it will likely to be placed into the generic "Bundles" component. This will make an already crowded component even more crowded. Should we consider creating a more diverse set of components for the work which is graduated into Equinox? I think the p2 and security work will deserve their own component when they graduate. Thoughts? Tom _______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/equinox-dev
Attachment:
pic01850.gif
Description: GIF image
