Re: [equinox-dev] shell refactoring proposal - Gogo jars in orbit
Much of this info is in the Orbit FAQ (http://wiki.eclipse.org/Orbit_Faq) Summary: We need to get a Orbit committer who will support Gogo in Orbit. They then enter a CQ that piggybacks on the orginal. Then once that is approved they (the committer) puts the Gogo in Orbit and away we go. To that end, I have recruited DJ to manage Gogo in Orbit. He entered CQ 4690 and will put Gogo in the Orbit builds etc when it is approved. Jeff On 2010-12-08, at 3:37 AM, Kirchev, Lazar wrote: Gogo jars are approved for use in equinox incubator (CQ 4561), but now what should be done in order to include them in orbit? File another CQ to request this? Lazar From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Jeff McAffer Sent: Thursday, December 02, 2010 4:11 PM To: Equinox development mailing list Subject: Re: [equinox-dev] shell refactoring proposal - Indigo plan deadline I'm not sure how to deal with the gogo jars in orbit. The jars are real bundles and we will not have to repackage them or anything like that. Jeff what do you recommend? Orbit is about maintaining bundles for third party code that eclipse projects use. We already have cases where the code is delivered to us as a bundle (ICU, SSH, ...) so this would be just another instance of this. As for timing, we have to wait for the IP team to approve the CQ but it should be reasonably quick. I do not plan to move the console out of the framework. We can provide any changes you need to be able to disable it completely in your environment. I think there are options to do this already. I guess the trick is if we expect someone running eclipse -console to get the built in one in one case and Gogo in another. What are we expecting the user model to be? Jeff ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] shell refactoring proposal - Gogo jars in orbit
Another option is to nominate Lazar as an Orbit committer if Lazar is up for maintaining Gogo in orbit. Tom | | From: | | ---| |Jeff McAffer j...@eclipsesource.com | ---| | | To:| | ---| |Equinox development mailing list equinox-dev@eclipse.org | ---| | | Date: | | ---| |12/09/2010 08:33 AM | ---| | | Subject: | | ---| |Re: [equinox-dev] shell refactoring proposal - Gogo jars in orbit | ---| Much of this info is in the Orbit FAQ (http://wiki.eclipse.org/Orbit_Faq) Summary: We need to get a Orbit committer who will support Gogo in Orbit. They then enter a CQ that piggybacks on the orginal. Then once that is approved they (the committer) puts the Gogo in Orbit and away we go. To that end, I have recruited DJ to manage Gogo in Orbit. He entered CQ 4690 and will put Gogo in the Orbit builds etc when it is approved. Jeff On 2010-12-08, at 3:37 AM, Kirchev, Lazar wrote: Gogo jars are approved for use in equinox incubator (CQ 4561), but now what should be done in order to include them in orbit? File another CQ to request this? Lazar From: equinox-dev-boun...@eclipse.org [ mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Jeff McAffer Sent: Thursday, December 02, 2010 4:11 PM To: Equinox development mailing list Subject: Re: [equinox-dev] shell refactoring proposal - Indigo plan deadline I'm not sure how to deal with the gogo jars in orbit. The jars are real bundles and we will not have to repackage them or anything like that. Jeff what do you recommend? Orbit is about maintaining bundles for third party code that eclipse projects use. We already have cases where the code is delivered to us as a bundle (ICU, SSH, ...) so this would be just another instance of this. As for timing, we have to wait for the IP team to approve the CQ but it should be reasonably quick. I do not plan to move the console out of the framework. We can provide any changes you need to be able to disable it completely in your environment. I think there are options to do this already. I guess the trick is if we expect someone running eclipse -console to get the built in one in one case and Gogo in another. What are we expecting the user model to be? Jeff ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] shell refactoring proposal - Gogo jars in orbit
Regarding the console work in the incubator, I will need Gogo and I will have to keep it up-to-date. So I can also maintain it in Orbit. Lazar From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: Thursday, December 09, 2010 4:52 PM To: Equinox development mailing list Subject: Re: [equinox-dev] shell refactoring proposal - Gogo jars in orbit Another option is to nominate Lazar as an Orbit committer if Lazar is up for maintaining Gogo in orbit. Tom [cid:image001.gif@01CB97C6.101A7800]Jeff McAffer ---12/09/2010 08:33:51 AM---Much of this info is in the Orbit FAQ ( http://wiki.eclipse.org/Orbit_Faq From: Jeff McAffer j...@eclipsesource.com To: Equinox development mailing list equinox-dev@eclipse.org Date: 12/09/2010 08:33 AM Subject: Re: [equinox-dev] shell refactoring proposal - Gogo jars in orbit Much of this info is in the Orbit FAQ (http://wiki.eclipse.org/Orbit_Faq) Summary: We need to get a Orbit committer who will support Gogo in Orbit. They then enter a CQ that piggybacks on the orginal. Then once that is approved they (the committer) puts the Gogo in Orbit and away we go. To that end, I have recruited DJ to manage Gogo in Orbit. He entered CQ 4690http://dev.eclipse.org/ipzilla/show_bug.cgi?id=4690 and will put Gogo in the Orbit builds etc when it is approved. Jeff On 2010-12-08, at 3:37 AM, Kirchev, Lazar wrote: Gogo jars are approved for use in equinox incubator (CQ 4561), but now what should be done in order to include them in orbit? File another CQ to request this? Lazar From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Jeff McAffer Sent: Thursday, December 02, 2010 4:11 PM To: Equinox development mailing list Subject: Re: [equinox-dev] shell refactoring proposal - Indigo plan deadline I'm not sure how to deal with the gogo jars in orbit. The jars are real bundles and we will not have to repackage them or anything like that. Jeff what do you recommend? Orbit is about maintaining bundles for third party code that eclipse projects use. We already have cases where the code is delivered to us as a bundle (ICU, SSH, ...) so this would be just another instance of this. As for timing, we have to wait for the IP team to approve the CQ but it should be reasonably quick. I do not plan to move the console out of the framework. We can provide any changes you need to be able to disable it completely in your environment. I think there are options to do this already. I guess the trick is if we expect someone running eclipse -console to get the built in one in one case and Gogo in another. What are we expecting the user model to be? Jeff ___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: image001.gifinline: image002.pnginline: image003.png___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
