Re: [cross-project-issues-dev] Status and Outlook for Luna M1
Hi Grégoire, The editor validated, so I hope the build will pass too. ATL and Acceleo have now been reenabled for Luna, though that will only be useful for M2 now. Laurent Goubet Obeo On 02/09/2013 16:34, Laurent Goubet wrote: Disabling all projects every year will always cause such issues : the Acceleo team was in holidays for most of August, which makes us "miss" M1. The same goes for ATL. Per change, we had one of the EMF Compare Team at hand to activate that one contribution (and even still, he had to tweak our build to manually remove features for which our dependencies are also marked as disabled). I think that leaving the contributions "enabled" would be better than forcing everyone into this situation : we have to load the aggregator, enable our contribution, check if it works... and come back at regular intervals to check for our dependencies' enablement. This is time consuming for those of us who depend on a few projects... and frustrating since we know that we are in turn blocking others. Not to mention that this always comes at a time where most of us are in holidays and just cannot react. I think this had already been discussed last year, and I do not know if leaving all projects "enabled" by default is better, at least it would not block anything. Grégoire, Acceleo will be enabled some time tomorrow (CEST), sorry for the wait. Laurent Goubet Obeo On 22/08/2013 18:11, Grégoire Dupé wrote: Hello I'm still waiting for Acceleo and ATL (may be more) to deliver MoDisco. It's quite late in Europe; I've to leave the office. I assume that MoDisco will not be included in Luna M1 :-( Regards, Grégoire - Original Message - From: "David M Williams" To: cross-project-issues-dev@eclipse.org Sent: Jeudi 22 Août 2013 10:13:05 Subject: [cross-project-issues-dev] Status and Outlook for Luna M1 Ok, it's Thursday morning :) Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done). That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on, but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet. Which brings me to my main point. Scanning the list of 22 disabled contributions, I'd guess about half are "leaf" components, so if you don't get enabled, it'd hurt no one but your self ... and maybe community and adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf ones? and DLTK are definitely "building blocks" that need to be enabled or else others downstream can not function or be enabled. If you are a "consuming" project and need some of those lower level ones enabled, I'd encourage a lot of "project-to-project" communication so they know how much you depend on them, and the effect they have by being "late" or incomplete, etc. So, I'm just asking everyone to be aware of your place in the eco system and plan accordingly. I suspect I'm just stating the obvious ... but not sure what else I can do to help. Thanks, = = = = = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev <>___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and Outlook for Luna M1
+1 That would have saved me hours and many aggregation cycles to figure out what's all missing. Cheers /Eike http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper Am 02.09.2013 16:34, schrieb Laurent Goubet: Disabling all projects every year will always cause such issues : the Acceleo team was in holidays for most of August, which makes us "miss" M1. The same goes for ATL. Per change, we had one of the EMF Compare Team at hand to activate that one contribution (and even still, he had to tweak our build to manually remove features for which our dependencies are also marked as disabled). I think that leaving the contributions "enabled" would be better than forcing everyone into this situation : we have to load the aggregator, enable our contribution, check if it works... and come back at regular intervals to check for our dependencies' enablement. This is time consuming for those of us who depend on a few projects... and frustrating since we know that we are in turn blocking others. Not to mention that this always comes at a time where most of us are in holidays and just cannot react. I think this had already been discussed last year, and I do not know if leaving all projects "enabled" by default is better, at least it would not block anything. Grégoire, Acceleo will be enabled some time tomorrow (CEST), sorry for the wait. Laurent Goubet Obeo On 22/08/2013 18:11, Grégoire Dupé wrote: Hello I'm still waiting for Acceleo and ATL (may be more) to deliver MoDisco. It's quite late in Europe; I've to leave the office. I assume that MoDisco will not be included in Luna M1 :-( Regards, Grégoire - Original Message - From: "David M Williams" To: cross-project-issues-dev@eclipse.org Sent: Jeudi 22 Août 2013 10:13:05 Subject: [cross-project-issues-dev] Status and Outlook for Luna M1 Ok, it's Thursday morning :) Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done). That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on, but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet. Which brings me to my main point. Scanning the list of 22 disabled contributions, I'd guess about half are "leaf" components, so if you don't get enabled, it'd hurt no one but your self ... and maybe community and adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf ones? and DLTK are definitely "building blocks" that need to be enabled or else others downstream can not function or be enabled. If you are a "consuming" project and need some of those lower level ones enabled, I'd encourage a lot of "project-to-project" communication so they know how much you depend on them, and the effect they have by being "late" or incomplete, etc. So, I'm just asking everyone to be aware of your place in the eco system and plan accordingly. I suspect I'm just stating the obvious ... but not sure what else I can do to help. Thanks, = = = = = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and Outlook for Luna M1
+1 This causes more pain on the community than it solves. Mind you I said that last year too. At the end of the day, I pushed our last kepler build into Luna M1, which is what would have happened by default. Sent from my BlackBerry 10 smartphone on the Rogers network. From: Laurent Goubet Sent: Monday, September 2, 2013 10:35 AM To: cross-project-issues-dev@eclipse.org Reply To: laurent.gou...@obeo.fr Subject: Re: [cross-project-issues-dev] Status and Outlook for Luna M1 Disabling all projects every year will always cause such issues : the Acceleo team was in holidays for most of August, which makes us "miss" M1. The same goes for ATL. Per change, we had one of the EMF Compare Team at hand to activate that one contribution (and even still, he had to tweak our build to manually remove features for which our dependencies are also marked as disabled). I think that leaving the contributions "enabled" would be better than forcing everyone into this situation : we have to load the aggregator, enable our contribution, check if it works... and come back at regular intervals to check for our dependencies' enablement. This is time consuming for those of us who depend on a few projects... and frustrating since we know that we are in turn blocking others. Not to mention that this always comes at a time where most of us are in holidays and just cannot react. I think this had already been discussed last year, and I do not know if leaving all projects "enabled" by default is better, at least it would not block anything. Grégoire, Acceleo will be enabled some time tomorrow (CEST), sorry for the wait. Laurent Goubet Obeo On 22/08/2013 18:11, Grégoire Dupé wrote: > Hello > > I'm still waiting for Acceleo and ATL (may be more) to deliver MoDisco. > > It's quite late in Europe; I've to leave the office. > > I assume that MoDisco will not be included in Luna M1 :-( > > Regards, > Grégoire > > - Original Message - > From: "David M Williams" > To: cross-project-issues-dev@eclipse.org > Sent: Jeudi 22 Août 2013 10:13:05 > Subject: [cross-project-issues-dev] Status and Outlook for Luna M1 > > > Ok, it's Thursday morning :) > > Only a few more have been enabled, but that includes DTP and BIRT, so that > should help Luna (Kepler RC1 repo is already considered done). > > That allowed me to enabled the "JPA" portions of WTP (since depends on > DataTools) which, I noticed, some others depended on, > but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on > Graphiti, which is not enabled yet. > > Which brings me to my main point. Scanning the list of 22 disabled > contributions, I'd guess about half are "leaf" components, so if you don't > get enabled, it'd hurt no one but your self ... and maybe community and > adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf > ones? and DLTK are definitely "building blocks" that need to be enabled or > else others downstream can not function or be enabled. If you are a > "consuming" project and need some of those lower level ones enabled, I'd > encourage a lot of "project-to-project" communication so they know how much > you depend on them, and the effect they have by being "late" or incomplete, > etc. > > So, I'm just asking everyone to be aware of your place in the eco system and > plan accordingly. I suspect I'm just stating the obvious ... but not sure > what else I can do to help. > > Thanks, > > = = = = = = = = = > > > actf.b3aggrcon - org.eclipse.simrel.build > amalgam.b3aggrcon - org.eclipse.simrel.build > amp.b3aggrcon - org.eclipse.simrel.build > dltk.b3aggrcon - org.eclipse.simrel.build > ecf.b3aggrcon - org.eclipse.simrel.build > emf-compare.b3aggrcon - org.eclipse.simrel.build > emft-ecoretools.b3aggrcon - org.eclipse.simrel.build > emft-eef.b3aggrcon - org.eclipse.simrel.build > emft-egf.b3aggrcon - org.eclipse.simrel.build > gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build > gmp-graphiti.b3aggrcon - org.eclipse.simrel.build > jwt.b3aggrcon - org.eclipse.simrel.build > koneki.b3aggrcon - org.eclipse.simrel.build > m2m-atl.b3aggrcon - org.eclipse.simrel.build > m2t-acceleo.b3aggrcon - org.eclipse.simrel.build > mdt-modisco.b3aggrcon - org.eclipse.simrel.build > mft.b3aggrcon - org.eclipse.simrel.build > mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build > pdt.b3aggrcon - org.eclipse.simrel.build > soa-bpel.b3aggrcon - org.eclipse.simrel.build > soa-sca.b3aggrcon - org.eclipse.simrel.build > windowbuilder.b3aggrcon - org.eclipse.simrel.build > > ___ > cr
Re: [cross-project-issues-dev] Status and Outlook for Luna M1
Disabling all projects every year will always cause such issues : the Acceleo team was in holidays for most of August, which makes us "miss" M1. The same goes for ATL. Per change, we had one of the EMF Compare Team at hand to activate that one contribution (and even still, he had to tweak our build to manually remove features for which our dependencies are also marked as disabled). I think that leaving the contributions "enabled" would be better than forcing everyone into this situation : we have to load the aggregator, enable our contribution, check if it works... and come back at regular intervals to check for our dependencies' enablement. This is time consuming for those of us who depend on a few projects... and frustrating since we know that we are in turn blocking others. Not to mention that this always comes at a time where most of us are in holidays and just cannot react. I think this had already been discussed last year, and I do not know if leaving all projects "enabled" by default is better, at least it would not block anything. Grégoire, Acceleo will be enabled some time tomorrow (CEST), sorry for the wait. Laurent Goubet Obeo On 22/08/2013 18:11, Grégoire Dupé wrote: Hello I'm still waiting for Acceleo and ATL (may be more) to deliver MoDisco. It's quite late in Europe; I've to leave the office. I assume that MoDisco will not be included in Luna M1 :-( Regards, Grégoire - Original Message - From: "David M Williams" To: cross-project-issues-dev@eclipse.org Sent: Jeudi 22 Août 2013 10:13:05 Subject: [cross-project-issues-dev] Status and Outlook for Luna M1 Ok, it's Thursday morning :) Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done). That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on, but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet. Which brings me to my main point. Scanning the list of 22 disabled contributions, I'd guess about half are "leaf" components, so if you don't get enabled, it'd hurt no one but your self ... and maybe community and adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf ones? and DLTK are definitely "building blocks" that need to be enabled or else others downstream can not function or be enabled. If you are a "consuming" project and need some of those lower level ones enabled, I'd encourage a lot of "project-to-project" communication so they know how much you depend on them, and the effect they have by being "late" or incomplete, etc. So, I'm just asking everyone to be aware of your place in the eco system and plan accordingly. I suspect I'm just stating the obvious ... but not sure what else I can do to help. Thanks, = = = = = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev <>___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and Outlook for Luna M1
Hi, As it seems I forgot to set the enabled flag to true before my vacation. That was the reason why Graphiti was not enabled so far. Anyhow, I just enabled the Graphiti contribution for Luna. Sorry for any inconveniences caused by this oversight… Michael From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Matthias Sohn Sent: Donnerstag, 22. August 2013 15:22 To: Cross project issues Subject: Re: [cross-project-issues-dev] Status and Outlook for Luna M1 On Thu, Aug 22, 2013 at 10:13 AM, David M Williams mailto:david_willi...@us.ibm.com>> wrote: Ok, it's Thursday morning :) Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done). That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on, but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet. Michael Wenz (Graphiti lead) is in vacation until next Monday. I guess that's the reason why Graphiti isn't yet enabled. -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Status and Outlook for Luna M1 -- last call ...
The "rate of contributions" appears to have crawled to a halt for Luna M1. All but 20 have enabled their contributions. Most of the other 50 are "fully enabled" (all but 8, which have some disabled feature or repository). I will wait until 5 PM Eastern to declare "staging repo done" if no one ask for more time. Not sure what magic Markus can do with EPP packages with what's enabled but, but I know at least "Eclipse Standard" should build :) Just wanted to let you know one last change to try to join in now before we close out M1. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and Outlook for Luna M1
Hello I'm still waiting for Acceleo and ATL (may be more) to deliver MoDisco. It's quite late in Europe; I've to leave the office. I assume that MoDisco will not be included in Luna M1 :-( Regards, Grégoire - Original Message - From: "David M Williams" To: cross-project-issues-dev@eclipse.org Sent: Jeudi 22 Août 2013 10:13:05 Subject: [cross-project-issues-dev] Status and Outlook for Luna M1 Ok, it's Thursday morning :) Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done). That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on, but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet. Which brings me to my main point. Scanning the list of 22 disabled contributions, I'd guess about half are "leaf" components, so if you don't get enabled, it'd hurt no one but your self ... and maybe community and adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf ones? and DLTK are definitely "building blocks" that need to be enabled or else others downstream can not function or be enabled. If you are a "consuming" project and need some of those lower level ones enabled, I'd encourage a lot of "project-to-project" communication so they know how much you depend on them, and the effect they have by being "late" or incomplete, etc. So, I'm just asking everyone to be aware of your place in the eco system and plan accordingly. I suspect I'm just stating the obvious ... but not sure what else I can do to help. Thanks, = = = = = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and Outlook for Luna M1
On Thu, Aug 22, 2013 at 10:13 AM, David M Williams < david_willi...@us.ibm.com> wrote: > Ok, it's Thursday morning :) > > Only a few more have been enabled, but that includes DTP and BIRT, so that > should help Luna (Kepler RC1 repo is already considered done). > > That allowed me to enabled the "JPA" portions of WTP (since depends on > DataTools) which, I noticed, some others depended on, > but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on > Graphiti, which is not enabled yet. Michael Wenz (Graphiti lead) is in vacation until next Monday. I guess that's the reason why Graphiti isn't yet enabled. -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Status and Outlook for Luna M1
Ok, it's Thursday morning :) Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done). That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on, but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet. Which brings me to my main point. Scanning the list of 22 disabled contributions, I'd guess about half are "leaf" components, so if you don't get enabled, it'd hurt no one but your self ... and maybe community and adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf ones? and DLTK are definitely "building blocks" that need to be enabled or else others downstream can not function or be enabled. If you are a "consuming" project and need some of those lower level ones enabled, I'd encourage a lot of "project-to-project" communication so they know how much you depend on them, and the effect they have by being "late" or incomplete, etc. So, I'm just asking everyone to be aware of your place in the eco system and plan accordingly. I suspect I'm just stating the obvious ... but not sure what else I can do to help. Thanks, = = = = = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Status and Outlook for Luna M1 -- please continue ...
We actually have gotten some green builds, and there is a "staging repo" at http://download.eclipse.org/releases/staging/ But it is only about half complete. 503 features and 2611 bundles (compared to Kepler, which has 946 features, and 4870 bundles). There are still 25 project files with disabled contributions ... and more than that, if you count disabled feature or repositories. While the deadline was today, at 5:00, here is plan B: We'll extend the deadline another day, to see if we can get a more complete aggregation repository. If so, there might be some possibility Markus would have "enough pieces" to build at least some EPP packages by late Friday (but, not sure that leaves enough time to call them tested). If not ... if we do not get enough contributions ... we will just count M1 as "failed to deliver" and move on to M2.. So, point is, if you are not yet enabled for Luna M1, please do so. If any of your "pre-req projects" are blocking you from making progress ... please let them know. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Thanks! On Aug 21, 2013, at 3:39 PM, David Dykstal wrote: > It exists now. > http://download.eclipse.org/tm/updates/3.6milestones/ > > -- David Dykstal, Architect - Rational Developer for i > > > > From:Greg Watson > To:Cross project issues , > Date:08/21/2013 01:45 PM > Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 > Sent by:cross-project-issues-dev-boun...@eclipse.org > > > > Does TM have a luna repo somewhere? I can't seem to find one. > > Thanks, > Greg > > On Aug 21, 2013, at 1:14 PM, David Dykstal wrote: > > > I have enabled TM. > > > > Doug Schaefer wrote: > >> Sigh. RSE isn't enabled so CDT fails. > >> > > ___ > > cross-project-issues-dev mailing list > > cross-project-issues-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
It exists now. http://download.eclipse.org/tm/updates/3.6milestones/ -- David Dykstal, Architect - Rational Developer for i From: Greg Watson To: Cross project issues , Date: 08/21/2013 01:45 PM Subject:Re: [cross-project-issues-dev] Status and outlook for Luna M1 Sent by:cross-project-issues-dev-boun...@eclipse.org Does TM have a luna repo somewhere? I can't seem to find one. Thanks, Greg On Aug 21, 2013, at 1:14 PM, David Dykstal wrote: > I have enabled TM. > > Doug Schaefer wrote: >> Sigh. RSE isn't enabled so CDT fails. >> > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Not to join would be a disservice to the community. Glad you allow us in. :) Sent from my BlackBerry 10 smartphone on the Rogers network. From: David M Williams Sent: Wednesday, August 21, 2013 2:54 PM To: Cross project issues Reply To: Cross project issues Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 I've enabled most of WTP (and yes, Carl asked me specifically to cover for him :) ... I enabled all the pieces that do not depend on DTP (e.g. JPA) ... so that should get us a little further. My local "validation" worked in editor and we'll see how the Hudson aggregation goes. Unfortunately -- from the poking around I've done -- DTP (and BIRT) likely won't be enabled/updated until 7 or 8 Eastern time at the earliest ... due to timezone differences ... so a) don't worry about getting lots of failures the rest of the day ... I know all the email "build break reminders" drives people crazy. But, b) we will still try to have a relatively complete repo for M1 but not sure there will be time to do EPP packages ... but ... I am forever optimistic -- believe it or not. We are currently down to 27 (from yesterday's 50) projects that have not enabled their contribution. (List below) Unfortunately many of those (like DTP) are depended on by many others so I remind you "low level" projects you are holding up others! @Igor, and others, the advantage to enabling contribution even if you leave repo disabled due to missing pre-reqs is just a matter of helping me (and others) track the current state and likelihood of making the goal. If, by Thursday morning, there are still, say 20, who have not even bothered to enable contribution, I'd be prone to conclude "no way". Whereas if all contributions were enabled, and just some features were not yet "fitting together", I might be more optimistic it could be worked out by end of Thursday. [Since you asked "why bother".] @Doug, and others ... no problem at all for me to set enabled="false" ... and, you know, I can never tell about CDT -- if they'll be the release or not ... glad you decided to join! :) = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build dtp.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build epp-mpc.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2e-wtp.b3aggrcon - org.eclipse.simrel.build m2e.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build From:"Konstantin Komissarchik" To: "'Cross project issues'" , Date:08/21/2013 02:29 PM Subject:Re: [cross-project-issues-dev] Status and outlook for Luna M1 Sent by:cross-project-issues-dev-boun...@eclipse.org Sapphire contribution is waiting on WTP contribution, which is waiting on DTP contribution. Disabling higher-level contributions until all the dependencies have been contributed is one option, but creates a lot of churn and forces a linear contribution path that guarantees that M1 repo is going to be quite thin. If WTP is still not contributed by the end of the day, I will disable Sapphire, but I am not sure how many EPP packages can be created from a repository in such a state… - Konstantin From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Oberhuber, Martin Sent: Wednesday, August 21, 2013 10:36 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 I have “declared intent” for tcf-1.2 by enabling the contribution … but will keep the repo disabled until the build is green. The build has been failing since 11.01am server time today so I’m not sure if it’s a good idea adding more contributions before it is green … in the end, someone (David?) would need to disable culprits. FWIW, when running the “validate aggregation” in the b3 model editor I get this er
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Make that 26, I've enabled MPC now. Sorry to be this late to the party. On 21.08.2013 20:53, David M Williams wrote: > We are currently down to 27 (from yesterday's 50) projects that have not > enabled their contribution. (List below) Unfortunately many of those (like > DTP) are depended on by many others so I remind you "low level" projects > you are holding up others! ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
I've enabled most of WTP (and yes, Carl asked me specifically to cover for him :) ... I enabled all the pieces that do not depend on DTP (e.g. JPA) ... so that should get us a little further. My local "validation" worked in editor and we'll see how the Hudson aggregation goes. Unfortunately -- from the poking around I've done -- DTP (and BIRT) likely won't be enabled/updated until 7 or 8 Eastern time at the earliest ... due to timezone differences ... so a) don't worry about getting lots of failures the rest of the day ... I know all the email "build break reminders" drives people crazy. But, b) we will still try to have a relatively complete repo for M1 but not sure there will be time to do EPP packages ... but ... I am forever optimistic -- believe it or not. We are currently down to 27 (from yesterday's 50) projects that have not enabled their contribution. (List below) Unfortunately many of those (like DTP) are depended on by many others so I remind you "low level" projects you are holding up others! @Igor, and others, the advantage to enabling contribution even if you leave repo disabled due to missing pre-reqs is just a matter of helping me (and others) track the current state and likelihood of making the goal. If, by Thursday morning, there are still, say 20, who have not even bothered to enable contribution, I'd be prone to conclude "no way". Whereas if all contributions were enabled, and just some features were not yet "fitting together", I might be more optimistic it could be worked out by end of Thursday. [Since you asked "why bother".] @Doug, and others ... no problem at all for me to set enabled="false" ... and, you know, I can never tell about CDT -- if they'll be the release or not ... glad you decided to join! :) = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build dtp.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build epp-mpc.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2e-wtp.b3aggrcon - org.eclipse.simrel.build m2e.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build From: "Konstantin Komissarchik" To: "'Cross project issues'" , Date: 08/21/2013 02:29 PM Subject:Re: [cross-project-issues-dev] Status and outlook for Luna M1 Sent by:cross-project-issues-dev-boun...@eclipse.org Sapphire contribution is waiting on WTP contribution, which is waiting on DTP contribution. Disabling higher-level contributions until all the dependencies have been contributed is one option, but creates a lot of churn and forces a linear contribution path that guarantees that M1 repo is going to be quite thin. If WTP is still not contributed by the end of the day, I will disable Sapphire, but I am not sure how many EPP packages can be created from a repository in such a state… - Konstantin From: cross-project-issues-dev-boun...@eclipse.org [ mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Oberhuber, Martin Sent: Wednesday, August 21, 2013 10:36 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 I have “declared intent” for tcf-1.2 by enabling the contribution … but will keep the repo disabled until the build is green. The build has been failing since 11.01am server time today so I’m not sure if it’s a good idea adding more contributions before it is green … in the end, someone (David?) would need to disable culprits. FWIW, when running the “validate aggregation” in the b3 model editor I get this error right now: Cannot complete the install because one or more required items could not be found. Missing requirement: Sapphire XML Editor Support (Incubation) 0.7.0.201308211148 (org.eclipse.sapphire.ui.swt.xml.editor 0.7.0.201308211148) requires 'bundle org.eclipse.wst.sse.core [1.1.600,2.0.0)' but it could not be found Bundle(org.eclipse.wst.s
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Does TM have a luna repo somewhere? I can't seem to find one. Thanks, Greg On Aug 21, 2013, at 1:14 PM, David Dykstal wrote: > I have enabled TM. > > Doug Schaefer wrote: >> Sigh. RSE isn't enabled so CDT fails. >> > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Sapphire contribution is waiting on WTP contribution, which is waiting on DTP contribution. Disabling higher-level contributions until all the dependencies have been contributed is one option, but creates a lot of churn and forces a linear contribution path that guarantees that M1 repo is going to be quite thin. If WTP is still not contributed by the end of the day, I will disable Sapphire, but I am not sure how many EPP packages can be created from a repository in such a state. - Konstantin From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Oberhuber, Martin Sent: Wednesday, August 21, 2013 10:36 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 I have "declared intent" for tcf-1.2 by enabling the contribution . but will keep the repo disabled until the build is green. The build has been failing since 11.01am server time today so I'm not sure if it's a good idea adding more contributions before it is green . in the end, someone (David?) would need to disable culprits. FWIW, when running the "validate aggregation" in the b3 model editor I get this error right now: Cannot complete the install because one or more required items could not be found. Missing requirement: Sapphire XML Editor Support (Incubation) 0.7.0.201308211148 (org.eclipse.sapphire.ui.swt.xml.editor 0.7.0.201308211148) requires 'bundle org.eclipse.wst.sse.core [1.1.600,2.0.0)' but it could not be found Bundle(org.eclipse.wst.sse.core [1.1.600,2.0.0)) is required by: ValidationSet(main) Contribution(Sapphire) MappedRepository(http://download.eclipse.org/sapphire/0.7.0.201308211148/rep ository) Feature(org.eclipse.sapphire.ui.swt.xml.editor.feature.group 0.7.0) InstallableUnit(org.eclipse.sapphire.ui.swt.xml.editor 0.7.0.201308211148) Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David M Williams Sent: Wednesday, August 21, 2013 6:01 AM To: cross-project-issues-dev@eclipse.org Subject: [cross-project-issues-dev] Status and outlook for Luna M1 Doesn't look good. I'll admit there is one day left, but so far 50 projects have not even enabled their "contribution" to Luna (pasted below). Thank you to the 20 of you who have. Remember, enable your contribution if you plan to participate (remove the "enabled="false"), but disable your repository if you are simply waiting for pre-reqs to get enabled or fixed (disable by adding enabled="false" to your repository element(s)). Please ask if questions. (Or, please say if you have explicitly decided not to participate in Luna). Thanks, = = = = = This list are those that have not yet enabled contribution: actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build cdt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build dtp.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build egit.b3aggrcon - org.eclipse.simrel.build emf-cdo.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emf-diffmerge.b3aggrcon - org.eclipse.simrel.build emf-query.b3aggrcon - org.eclipse.simrel.build emf-transaction.b3aggrcon - org.eclipse.simrel.build emf-validation.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build emft-emffacet.b3aggrcon - org.eclipse.simrel.build epp-mpc.b3aggrcon - org.eclipse.simrel.build gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jubula.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build linuxtools.b3aggrcon - org.eclipse.simrel.build m2e-wtp.b3aggrcon - org.eclipse.simrel.build m2e.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mat.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mdt-papyrus.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mmt-qvto.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build mylyn.b3aggrcon - org.eclipse.simrel.build objectteams.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build pt
Re: [cross-project-issues-dev] Status and outlook for Luna M1
I've enabled PTP now that CDT is enabled. Regards, Greg On Aug 21, 2013, at 12:00 AM, David M Williams wrote: > Doesn't look good. I'll admit there is one day left, but so far 50 projects > have not even enabled their "contribution" to Luna (pasted below). > > Thank you to the 20 of you who have. > > Remember, enable your contribution if you plan to participate (remove the > "enabled="false"), but disable your repository if you are simply waiting for > pre-reqs to get enabled or fixed (disable by adding enabled="false" to your > repository element(s)). > > Please ask if questions. (Or, please say if you have explicitly decided not > to participate in Luna). > > Thanks, > > = = = = = > > This list are those that have not yet enabled contribution: > > actf.b3aggrcon - org.eclipse.simrel.build > amalgam.b3aggrcon - org.eclipse.simrel.build > amp.b3aggrcon - org.eclipse.simrel.build > birt.b3aggrcon - org.eclipse.simrel.build > cdt.b3aggrcon - org.eclipse.simrel.build > dltk.b3aggrcon - org.eclipse.simrel.build > dtp.b3aggrcon - org.eclipse.simrel.build > ecf.b3aggrcon - org.eclipse.simrel.build > egit.b3aggrcon - org.eclipse.simrel.build > emf-cdo.b3aggrcon - org.eclipse.simrel.build > emf-compare.b3aggrcon - org.eclipse.simrel.build > emf-diffmerge.b3aggrcon - org.eclipse.simrel.build > emf-query.b3aggrcon - org.eclipse.simrel.build > emf-transaction.b3aggrcon - org.eclipse.simrel.build > emf-validation.b3aggrcon - org.eclipse.simrel.build > emft-ecoretools.b3aggrcon - org.eclipse.simrel.build > emft-eef.b3aggrcon - org.eclipse.simrel.build > emft-egf.b3aggrcon - org.eclipse.simrel.build > emft-emffacet.b3aggrcon - org.eclipse.simrel.build > epp-mpc.b3aggrcon - org.eclipse.simrel.build > gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build > gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build > gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build > gmp-graphiti.b3aggrcon - org.eclipse.simrel.build > jubula.b3aggrcon - org.eclipse.simrel.build > jwt.b3aggrcon - org.eclipse.simrel.build > koneki.b3aggrcon - org.eclipse.simrel.build > linuxtools.b3aggrcon - org.eclipse.simrel.build > m2e-wtp.b3aggrcon - org.eclipse.simrel.build > m2e.b3aggrcon - org.eclipse.simrel.build > m2m-atl.b3aggrcon - org.eclipse.simrel.build > m2t-acceleo.b3aggrcon - org.eclipse.simrel.build > mat.b3aggrcon - org.eclipse.simrel.build > mdt-modisco.b3aggrcon - org.eclipse.simrel.build > mdt-papyrus.b3aggrcon - org.eclipse.simrel.build > mft.b3aggrcon - org.eclipse.simrel.build > mmt-qvto.b3aggrcon - org.eclipse.simrel.build > mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build > mylyn.b3aggrcon - org.eclipse.simrel.build > objectteams.b3aggrcon - org.eclipse.simrel.build > pdt.b3aggrcon - org.eclipse.simrel.build > ptp.b3aggrcon - org.eclipse.simrel.build > sapphire.b3aggrcon - org.eclipse.simrel.build > scout-rap.b3aggrcon - org.eclipse.simrel.build > scout.b3aggrcon - org.eclipse.simrel.build > soa-bpel.b3aggrcon - org.eclipse.simrel.build > soa-sca.b3aggrcon - org.eclipse.simrel.build > tcf.b3aggrcon - org.eclipse.simrel.build > tm.b3aggrcon - org.eclipse.simrel.build > windowbuilder.b3aggrcon - org.eclipse.simrel.build > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
I have "declared intent" for tcf-1.2 by enabling the contribution ... but will keep the repo disabled until the build is green. The build has been failing since 11.01am server time today so I'm not sure if it's a good idea adding more contributions before it is green ... in the end, someone (David?) would need to disable culprits. FWIW, when running the "validate aggregation" in the b3 model editor I get this error right now: Cannot complete the install because one or more required items could not be found. Missing requirement: Sapphire XML Editor Support (Incubation) 0.7.0.201308211148 (org.eclipse.sapphire.ui.swt.xml.editor 0.7.0.201308211148) requires 'bundle org.eclipse.wst.sse.core [1.1.600,2.0.0)' but it could not be found Bundle(org.eclipse.wst.sse.core [1.1.600,2.0.0)) is required by: ValidationSet(main) Contribution(Sapphire) MappedRepository(http://download.eclipse.org/sapphire/0.7.0.201308211148/repository) Feature(org.eclipse.sapphire.ui.swt.xml.editor.feature.group 0.7.0) InstallableUnit(org.eclipse.sapphire.ui.swt.xml.editor 0.7.0.201308211148) Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David M Williams Sent: Wednesday, August 21, 2013 6:01 AM To: cross-project-issues-dev@eclipse.org Subject: [cross-project-issues-dev] Status and outlook for Luna M1 Doesn't look good. I'll admit there is one day left, but so far 50 projects have not even enabled their "contribution" to Luna (pasted below). Thank you to the 20 of you who have. Remember, enable your contribution if you plan to participate (remove the "enabled="false"), but disable your repository if you are simply waiting for pre-reqs to get enabled or fixed (disable by adding enabled="false" to your repository element(s)). Please ask if questions. (Or, please say if you have explicitly decided not to participate in Luna). Thanks, = = = = = This list are those that have not yet enabled contribution: actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build cdt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build dtp.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build egit.b3aggrcon - org.eclipse.simrel.build emf-cdo.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emf-diffmerge.b3aggrcon - org.eclipse.simrel.build emf-query.b3aggrcon - org.eclipse.simrel.build emf-transaction.b3aggrcon - org.eclipse.simrel.build emf-validation.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build emft-emffacet.b3aggrcon - org.eclipse.simrel.build epp-mpc.b3aggrcon - org.eclipse.simrel.build gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jubula.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build linuxtools.b3aggrcon - org.eclipse.simrel.build m2e-wtp.b3aggrcon - org.eclipse.simrel.build m2e.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mat.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mdt-papyrus.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mmt-qvto.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build mylyn.b3aggrcon - org.eclipse.simrel.build objectteams.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build ptp.b3aggrcon - org.eclipse.simrel.build sapphire.b3aggrcon - org.eclipse.simrel.build scout-rap.b3aggrcon - org.eclipse.simrel.build scout.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build tcf.b3aggrcon - org.eclipse.simrel.build tm.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
I have enabled TM. Doug Schaefer wrote: Sigh. RSE isn't enabled so CDT fails. ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
I believe m2e-wtp fails because the webtools contribution is disabled. On Wed, Aug 21, 2013 at 6:29 PM, Jeff Johnston wrote: > With CDT enabled, I have enabled Linux Tools. > > > On 08/21/2013 10:49 AM, Doug Schaefer wrote: > > I've re-enabled CDT. Sorry for wasting the time of the person who put > enabled="false" into our file. > > Doug. > > From: Sergey Boyko > Reply-To: Cross project issues > Date: Wednesday, 21 August, 2013 10:18 AM > To: Cross project issues > Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 > > QVTo was re-enabled for Luna. > > Cheers... > Sergey > > > On Wed, Aug 21, 2013 at 8:00 AM, David M Williams < > david_willi...@us.ibm.com> wrote: > >> Doesn't look good. I'll admit there is one day left, but so far 50 >> projects have not even enabled their "contribution" to Luna (pasted below). >> >> > > ___ > cross-project-issues-dev mailing > listcross-project-issues-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > -- "Have you tried turning it off and on again" - The IT Crowd ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
With CDT enabled, I have enabled Linux Tools. On 08/21/2013 10:49 AM, Doug Schaefer wrote: I've re-enabled CDT. Sorry for wasting the time of the person who put enabled="false" into our file. Doug. From: Sergey Boyko <mailto:serg.boyko2...@gmail.com>> Reply-To: Cross project issues <mailto:cross-project-issues-dev@eclipse.org>> Date: Wednesday, 21 August, 2013 10:18 AM To: Cross project issues <mailto:cross-project-issues-dev@eclipse.org>> Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 QVTo was re-enabled for Luna. Cheers... Sergey On Wed, Aug 21, 2013 at 8:00 AM, David M Williams mailto:david_willi...@us.ibm.com>> wrote: Doesn't look good. I'll admit there is one day left, but so far 50 projects have not even enabled their "contribution" to Luna (pasted below). ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Sigh. RSE isn't enabled so CDT fails. From: Doug Schaefer mailto:dschae...@qnx.com>> Reply-To: Cross project issues mailto:cross-project-issues-dev@eclipse.org>> Date: Wednesday, 21 August, 2013 10:49 AM To: Cross project issues mailto:cross-project-issues-dev@eclipse.org>> Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 I've re-enabled CDT. Sorry for wasting the time of the person who put enabled="false" into our file. Doug. From: Sergey Boyko mailto:serg.boyko2...@gmail.com>> Reply-To: Cross project issues mailto:cross-project-issues-dev@eclipse.org>> Date: Wednesday, 21 August, 2013 10:18 AM To: Cross project issues mailto:cross-project-issues-dev@eclipse.org>> Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 QVTo was re-enabled for Luna. Cheers... Sergey On Wed, Aug 21, 2013 at 8:00 AM, David M Williams mailto:david_willi...@us.ibm.com>> wrote: Doesn't look good. I'll admit there is one day left, but so far 50 projects have not even enabled their "contribution" to Luna (pasted below). ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
I've re-enabled CDT. Sorry for wasting the time of the person who put enabled="false" into our file. Doug. From: Sergey Boyko mailto:serg.boyko2...@gmail.com>> Reply-To: Cross project issues mailto:cross-project-issues-dev@eclipse.org>> Date: Wednesday, 21 August, 2013 10:18 AM To: Cross project issues mailto:cross-project-issues-dev@eclipse.org>> Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1 QVTo was re-enabled for Luna. Cheers... Sergey On Wed, Aug 21, 2013 at 8:00 AM, David M Williams mailto:david_willi...@us.ibm.com>> wrote: Doesn't look good. I'll admit there is one day left, but so far 50 projects have not even enabled their "contribution" to Luna (pasted below). ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
QVTo was re-enabled for Luna. Cheers... Sergey On Wed, Aug 21, 2013 at 8:00 AM, David M Williams wrote: > Doesn't look good. I'll admit there is one day left, but so far 50 > projects have not even enabled their "contribution" to Luna (pasted below). > > ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
> EMF Validation was re-enabled this morning EST. Thanks ! I've delivered EMF Facet. Regards, Grégoire ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
EMF Validation was re-enabled this morning EST. Cheers... Anthony From: Grégoire Dupé To: Cross project issues Date: 2013/08/21 09:27 AM Subject:Re: [cross-project-issues-dev] Status and outlook for Luna M1 Sent by:cross-project-issues-dev-boun...@eclipse.org Hello, I’m still not able to deliver EMF Facet and MoDisco because some dependences have not be re-enabled (at least org.eclipse.emf.validation). Regards, Grégoire ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Memory Analyzer is now also enabled. We disabled our charts feature, as it depends on BIRT, which is not yet enabled. I had troubles pushing (couldn't get through our corporate proxy). Thanks to Matthias who made the changes instead of me. From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David M Williams Sent: Mittwoch, 21. August 2013 06:01 To: cross-project-issues-dev@eclipse.org Subject: [cross-project-issues-dev] Status and outlook for Luna M1 Doesn't look good. I'll admit there is one day left, but so far 50 projects have not even enabled their "contribution" to Luna (pasted below). Thank you to the 20 of you who have. Remember, enable your contribution if you plan to participate (remove the "enabled="false"), but disable your repository if you are simply waiting for pre-reqs to get enabled or fixed (disable by adding enabled="false" to your repository element(s)). Please ask if questions. (Or, please say if you have explicitly decided not to participate in Luna). Thanks, = = = = = This list are those that have not yet enabled contribution: actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build cdt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build dtp.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build egit.b3aggrcon - org.eclipse.simrel.build emf-cdo.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emf-diffmerge.b3aggrcon - org.eclipse.simrel.build emf-query.b3aggrcon - org.eclipse.simrel.build emf-transaction.b3aggrcon - org.eclipse.simrel.build emf-validation.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build emft-emffacet.b3aggrcon - org.eclipse.simrel.build epp-mpc.b3aggrcon - org.eclipse.simrel.build gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jubula.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build linuxtools.b3aggrcon - org.eclipse.simrel.build m2e-wtp.b3aggrcon - org.eclipse.simrel.build m2e.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mat.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mdt-papyrus.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mmt-qvto.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build mylyn.b3aggrcon - org.eclipse.simrel.build objectteams.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build ptp.b3aggrcon - org.eclipse.simrel.build sapphire.b3aggrcon - org.eclipse.simrel.build scout-rap.b3aggrcon - org.eclipse.simrel.build scout.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build tcf.b3aggrcon - org.eclipse.simrel.build tm.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Hello, I’m still not able to deliver EMF Facet and MoDisco because some dependences have not be re-enabled (at least org.eclipse.emf.validation). Regards, Grégoire ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
On Wed, Aug 21, 2013 at 9:52 AM, Steffen Pingel wrote: > I have enabled Mylyn now. It should be in the latest build which took only > 8 minutes to complete (!). > > Steffen > > thanks, I reenabled the EGit features which are depending on Mylyn -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
On 2013-08-21 12:00 AM, David M Williams wrote: Remember, enable your contribution if you plan to participate (remove the "enabled="false"), but disable your repository if you are simply waiting for pre-reqs to get enabled or fixed (disable by adding enabled="false" to your repository element(s)). What's the point of this? I still need to manually check aggregator to see if my dependencies got enabled, so this appears to be an extra (admittedly tiny) bit of work I need to do that does not add much/any additional information. -- Regards, Igor ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
Object Teams cannot be installed in M1 due to https://bugs.eclipse.org/253244 (which hits us after the rewrite of the equinox framework). I will enable our contribution just for one aggregation run to see we're able to contribute and disable it immediately after. I'm hopeful that the bug can be settled with the p2 team in time for M2. best, Stephan On 08/21/2013 06:00 AM, David M Williams wrote: Doesn't look good. I'll admit there is one day left, but so far 50 projects have not even enabled their "contribution" to Luna (pasted below). Thank you to the 20 of you who have. Remember, enable your contribution if you plan to participate (remove the "enabled="false"), but disable your repository if you are simply waiting for pre-reqs to get enabled or fixed (disable by adding enabled="false" to your repository element(s)). Please ask if questions. (Or, please say if you have explicitly decided not to participate in Luna). Thanks, = = = = = This list are those that have not yet enabled contribution: actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build cdt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build dtp.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build egit.b3aggrcon - org.eclipse.simrel.build emf-cdo.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emf-diffmerge.b3aggrcon - org.eclipse.simrel.build emf-query.b3aggrcon - org.eclipse.simrel.build emf-transaction.b3aggrcon - org.eclipse.simrel.build emf-validation.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build emft-emffacet.b3aggrcon - org.eclipse.simrel.build epp-mpc.b3aggrcon - org.eclipse.simrel.build gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jubula.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build linuxtools.b3aggrcon - org.eclipse.simrel.build m2e-wtp.b3aggrcon - org.eclipse.simrel.build m2e.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mat.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mdt-papyrus.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mmt-qvto.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build mylyn.b3aggrcon - org.eclipse.simrel.build objectteams.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build ptp.b3aggrcon - org.eclipse.simrel.build sapphire.b3aggrcon - org.eclipse.simrel.build scout-rap.b3aggrcon - org.eclipse.simrel.build scout.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build tcf.b3aggrcon - org.eclipse.simrel.build tm.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
I have enabled Mylyn now. It should be in the latest build which took only 8 minutes to complete (!). Steffen On Wed, Aug 21, 2013 at 9:13 AM, Matthias Sohn wrote: > On Wed, Aug 21, 2013 at 6:00 AM, David M Williams < > david_willi...@us.ibm.com> wrote: > >> Doesn't look good. I'll admit there is one day left, but so far 50 >> projects have not even enabled their "contribution" to Luna (pasted below). >> >> Thank you to the 20 of you who have. >> >> Remember, enable your contribution if you plan to participate (remove the >> "enabled="false"), but disable your repository if you are simply waiting >> for pre-reqs to get enabled or fixed (disable by adding enabled="false" to >> your repository element(s)). >> >> Please ask if questions. (Or, please say if you have explicitly decided >> not to participate in Luna). >> >> Thanks, >> >> = = = = = >> >> This list are those that have not yet enabled contribution: >> >> actf.b3aggrcon - org.eclipse.simrel.build >> amalgam.b3aggrcon - org.eclipse.simrel.build >> amp.b3aggrcon - org.eclipse.simrel.build >> birt.b3aggrcon - org.eclipse.simrel.build >> cdt.b3aggrcon - org.eclipse.simrel.build >> dltk.b3aggrcon - org.eclipse.simrel.build >> dtp.b3aggrcon - org.eclipse.simrel.build >> ecf.b3aggrcon - org.eclipse.simrel.build >> egit.b3aggrcon - org.eclipse.simrel.build >> emf-cdo.b3aggrcon - org.eclipse.simrel.build >> emf-compare.b3aggrcon - org.eclipse.simrel.build >> emf-diffmerge.b3aggrcon - org.eclipse.simrel.build >> emf-query.b3aggrcon - org.eclipse.simrel.build >> emf-transaction.b3aggrcon - org.eclipse.simrel.build >> emf-validation.b3aggrcon - org.eclipse.simrel.build >> emft-ecoretools.b3aggrcon - org.eclipse.simrel.build >> emft-eef.b3aggrcon - org.eclipse.simrel.build >> emft-egf.b3aggrcon - org.eclipse.simrel.build >> emft-emffacet.b3aggrcon - org.eclipse.simrel.build >> epp-mpc.b3aggrcon - org.eclipse.simrel.build >> gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build >> gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build >> gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build >> gmp-graphiti.b3aggrcon - org.eclipse.simrel.build >> jubula.b3aggrcon - org.eclipse.simrel.build >> jwt.b3aggrcon - org.eclipse.simrel.build >> koneki.b3aggrcon - org.eclipse.simrel.build >> linuxtools.b3aggrcon - org.eclipse.simrel.build >> m2e-wtp.b3aggrcon - org.eclipse.simrel.build >> m2e.b3aggrcon - org.eclipse.simrel.build >> m2m-atl.b3aggrcon - org.eclipse.simrel.build >> m2t-acceleo.b3aggrcon - org.eclipse.simrel.build >> mat.b3aggrcon - org.eclipse.simrel.build >> mdt-modisco.b3aggrcon - org.eclipse.simrel.build >> mdt-papyrus.b3aggrcon - org.eclipse.simrel.build >> mft.b3aggrcon - org.eclipse.simrel.build >> mmt-qvto.b3aggrcon - org.eclipse.simrel.build >> mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build >> mylyn.b3aggrcon - org.eclipse.simrel.build >> objectteams.b3aggrcon - org.eclipse.simrel.build >> pdt.b3aggrcon - org.eclipse.simrel.build >> ptp.b3aggrcon - org.eclipse.simrel.build >> sapphire.b3aggrcon - org.eclipse.simrel.build >> scout-rap.b3aggrcon - org.eclipse.simrel.build >> scout.b3aggrcon - org.eclipse.simrel.build >> soa-bpel.b3aggrcon - org.eclipse.simrel.build >> soa-sca.b3aggrcon - org.eclipse.simrel.build >> tcf.b3aggrcon - org.eclipse.simrel.build >> tm.b3aggrcon - org.eclipse.simrel.build >> windowbuilder.b3aggrcon - org.eclipse.simrel.build >> > > I have enabled the EGit contribution though I had to disable the EGit > Mylyn integration > and the EGit GitHub connector contribution since Mylyn isn't yet in. > > -- > Matthias > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > -- Steffen Pingel Principal Software Engineer, Eclipse Mylyn Mylyn Tasks Lead http://tasktop.com ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Luna M1
On Wed, Aug 21, 2013 at 6:00 AM, David M Williams wrote: > Doesn't look good. I'll admit there is one day left, but so far 50 > projects have not even enabled their "contribution" to Luna (pasted below). > > Thank you to the 20 of you who have. > > Remember, enable your contribution if you plan to participate (remove the > "enabled="false"), but disable your repository if you are simply waiting > for pre-reqs to get enabled or fixed (disable by adding enabled="false" to > your repository element(s)). > > Please ask if questions. (Or, please say if you have explicitly decided > not to participate in Luna). > > Thanks, > > = = = = = > > This list are those that have not yet enabled contribution: > > actf.b3aggrcon - org.eclipse.simrel.build > amalgam.b3aggrcon - org.eclipse.simrel.build > amp.b3aggrcon - org.eclipse.simrel.build > birt.b3aggrcon - org.eclipse.simrel.build > cdt.b3aggrcon - org.eclipse.simrel.build > dltk.b3aggrcon - org.eclipse.simrel.build > dtp.b3aggrcon - org.eclipse.simrel.build > ecf.b3aggrcon - org.eclipse.simrel.build > egit.b3aggrcon - org.eclipse.simrel.build > emf-cdo.b3aggrcon - org.eclipse.simrel.build > emf-compare.b3aggrcon - org.eclipse.simrel.build > emf-diffmerge.b3aggrcon - org.eclipse.simrel.build > emf-query.b3aggrcon - org.eclipse.simrel.build > emf-transaction.b3aggrcon - org.eclipse.simrel.build > emf-validation.b3aggrcon - org.eclipse.simrel.build > emft-ecoretools.b3aggrcon - org.eclipse.simrel.build > emft-eef.b3aggrcon - org.eclipse.simrel.build > emft-egf.b3aggrcon - org.eclipse.simrel.build > emft-emffacet.b3aggrcon - org.eclipse.simrel.build > epp-mpc.b3aggrcon - org.eclipse.simrel.build > gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build > gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build > gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build > gmp-graphiti.b3aggrcon - org.eclipse.simrel.build > jubula.b3aggrcon - org.eclipse.simrel.build > jwt.b3aggrcon - org.eclipse.simrel.build > koneki.b3aggrcon - org.eclipse.simrel.build > linuxtools.b3aggrcon - org.eclipse.simrel.build > m2e-wtp.b3aggrcon - org.eclipse.simrel.build > m2e.b3aggrcon - org.eclipse.simrel.build > m2m-atl.b3aggrcon - org.eclipse.simrel.build > m2t-acceleo.b3aggrcon - org.eclipse.simrel.build > mat.b3aggrcon - org.eclipse.simrel.build > mdt-modisco.b3aggrcon - org.eclipse.simrel.build > mdt-papyrus.b3aggrcon - org.eclipse.simrel.build > mft.b3aggrcon - org.eclipse.simrel.build > mmt-qvto.b3aggrcon - org.eclipse.simrel.build > mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build > mylyn.b3aggrcon - org.eclipse.simrel.build > objectteams.b3aggrcon - org.eclipse.simrel.build > pdt.b3aggrcon - org.eclipse.simrel.build > ptp.b3aggrcon - org.eclipse.simrel.build > sapphire.b3aggrcon - org.eclipse.simrel.build > scout-rap.b3aggrcon - org.eclipse.simrel.build > scout.b3aggrcon - org.eclipse.simrel.build > soa-bpel.b3aggrcon - org.eclipse.simrel.build > soa-sca.b3aggrcon - org.eclipse.simrel.build > tcf.b3aggrcon - org.eclipse.simrel.build > tm.b3aggrcon - org.eclipse.simrel.build > windowbuilder.b3aggrcon - org.eclipse.simrel.build > I have enabled the EGit contribution though I had to disable the EGit Mylyn integration and the EGit GitHub connector contribution since Mylyn isn't yet in. -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Status and outlook for Luna M1
Doesn't look good. I'll admit there is one day left, but so far 50 projects have not even enabled their "contribution" to Luna (pasted below). Thank you to the 20 of you who have. Remember, enable your contribution if you plan to participate (remove the "enabled="false"), but disable your repository if you are simply waiting for pre-reqs to get enabled or fixed (disable by adding enabled="false" to your repository element(s)). Please ask if questions. (Or, please say if you have explicitly decided not to participate in Luna). Thanks, = = = = = This list are those that have not yet enabled contribution: actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build cdt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build dtp.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build egit.b3aggrcon - org.eclipse.simrel.build emf-cdo.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emf-diffmerge.b3aggrcon - org.eclipse.simrel.build emf-query.b3aggrcon - org.eclipse.simrel.build emf-transaction.b3aggrcon - org.eclipse.simrel.build emf-validation.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build emft-emffacet.b3aggrcon - org.eclipse.simrel.build epp-mpc.b3aggrcon - org.eclipse.simrel.build gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jubula.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build linuxtools.b3aggrcon - org.eclipse.simrel.build m2e-wtp.b3aggrcon - org.eclipse.simrel.build m2e.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mat.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mdt-papyrus.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mmt-qvto.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build mylyn.b3aggrcon - org.eclipse.simrel.build objectteams.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build ptp.b3aggrcon - org.eclipse.simrel.build sapphire.b3aggrcon - org.eclipse.simrel.build scout-rap.b3aggrcon - org.eclipse.simrel.build scout.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build tcf.b3aggrcon - org.eclipse.simrel.build tm.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
