Re: [cross-project-issues-dev] What policy w.r.t. javafx package imports?
Tom, at what offset can we expect the e(fx)clipse contribution? Will you contribute something to M1? Cheers Alexander Am 18.08.2014 um 21:59 schrieb Alexander Nyßen alexander.nys...@itemis.de: I temporarily disabled all GEF4 features that (directly or indirectly) depend on JavaFX. I do not know what is the intended offset of e(fx)clipse, but unless we find out how to provide these dependencies (i.e. jfxrt.jar in case of Java7, jfxswt.jar in case of Java8) to B3 directly (i.e. jfxrt.jar in case of Java7, jfxswt.jar in case of Java8) we will have to re-enable them after e(fx)clipse has joined (and potentially update our contribution). Cheers Alexander Am 18.08.2014 um 21:43 schrieb Alexander Nyßen alexander.nys...@itemis.de: Would that mean I have to specify dependencies to e(fx)clipse or would b3 resolve this implicitly? Up to now, my bundles only specify javafx package imports (including imports to javafx.embed.swt)... Cheers Alexander Am 18.08.2014 um 21:40 schrieb Tom Schindl tom.schi...@bestsolution.at: a) e(fx)clipse just released 1.0 b) the bundles required only depend on equinox = Luna So no matter if we (efxclipse) are on the Mars release GEF4 should be fine! Tom Von meinem iPhone gesendet Am 18.08.2014 um 21:22 schrieb David M Williams david_willi...@us.ibm.com: And, in the mean time, it seems your current contribution won't aggregate (and mentions missing things somehow related to fx. Can you disable those features for now? For the record, if the required project did not participate, you can include their features in yours, but, only from their latest released version (if there is one ... and if there is not a released version, then you could not do it). Thanks, From:Alexander Nyßen alexander.nys...@itemis.de To:Cross project issues cross-project-issues-dev@eclipse.org, Date:08/18/2014 12:58 PM Subject:[cross-project-issues-dev] What policy w.r.t. javafx packageimports? Sent by:cross-project-issues-dev-boun...@eclipse.org Hi all, as some of the new GEF4 bundles we want to include with Mars specify javafx package imports (so far without version constraints), I was wondering what general policy we want to follow to ensure such kind of bundles can be properly resolved. Should we rely on the e(fx)clipse runtime bundles/fragments (org.eclipse.javafx and org.eclipse.fx.osgi), i.e. re-bundle them in our features or specify feature-dependencies to the enclosing e(fx)clipse runtime feature, or is there another intended way (it seems, e(fx)clipse has not announced its participation)? Cheers Alexander -- Dr. Alexander Nyßen Dipl.-Inform. Software-Engineer Telefon: +49 (0) 231 / 98 60-210 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0) 151 / 17396743 http://www.itemis.de alexander.nys...@itemis.de itemis AG Am Brambusch 15-24 44536 Lünen Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus [attachment signature.asc deleted by David M Williams/Raleigh/IBM] ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Dr. Alexander Nyßen Dipl.-Inform. Software-Engineer Telefon: +49 (0) 231 / 98 60-210 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0) 151 / 17396743 http://www.itemis.de alexander.nys...@itemis.de itemis AG Am Brambusch 15-24 44536 Lünen Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Dr. Alexander Nyßen
[cross-project-issues-dev] e(fx)clipse participating in Mars release
Hi, e(fx)clipse would like to join the Mars release as a +3 component because we depend on Xtext who is +2. Our current plan is to contribute e(fx)clipse 2.0 because this is the first time we are joining (I need to make myself familiar with the process) I'm not sure we manage to contribute to M1 in time. Tom ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] What policy w.r.t. javafx package imports?
Hi, We'll join as +3 but I can not promise we manage to contribute to M1 already because I need to make myself familiar with the process, ... . Tom On 20.08.14 10:28, Alexander Nyßen wrote: Tom, at what offset can we expect the e(fx)clipse contribution? Will you contribute something to M1? Cheers Alexander Am 18.08.2014 um 21:59 schrieb Alexander Nyßen alexander.nys...@itemis.de mailto:alexander.nys...@itemis.de: I temporarily disabled all GEF4 features that (directly or indirectly) depend on JavaFX. I do not know what is the intended offset of e(fx)clipse, but unless we find out how to provide these dependencies (i.e. jfxrt.jar in case of Java7, jfxswt.jar in case of Java8) to B3 directly (i.e. jfxrt.jar in case of Java7, jfxswt.jar in case of Java8) we will have to re-enable them after e(fx)clipse has joined (and potentially update our contribution). Cheers Alexander Am 18.08.2014 um 21:43 schrieb Alexander Nyßen alexander.nys...@itemis.de mailto:alexander.nys...@itemis.de: Would that mean I have to specify dependencies to e(fx)clipse or would b3 resolve this implicitly? Up to now, my bundles only specify javafx package imports (including imports to javafx.embed.swt)... Cheers Alexander Am 18.08.2014 um 21:40 schrieb Tom Schindl tom.schi...@bestsolution.at mailto:tom.schi...@bestsolution.at: a) e(fx)clipse just released 1.0 b) the bundles required only depend on equinox = Luna So no matter if we (efxclipse) are on the Mars release GEF4 should be fine! Tom Von meinem iPhone gesendet Am 18.08.2014 um 21:22 schrieb David M Williams david_willi...@us.ibm.com mailto:david_willi...@us.ibm.com: And, in the mean time, it seems your current contribution won't aggregate (and mentions missing things somehow related to fx. Can you disable those features for now? For the record, if the required project did not participate, you can include their features in yours, but, only from their latest released version (if there is one ... and if there is not a released version, then you could not do it). Thanks, From:Alexander Nyßen alexander.nys...@itemis.de mailto:alexander.nys...@itemis.de To:Cross project issues cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org, Date:08/18/2014 12:58 PM Subject:[cross-project-issues-dev] What policy w.r.t. javafx packageimports? Sent by:cross-project-issues-dev-boun...@eclipse.org mailto:cross-project-issues-dev-boun...@eclipse.org Hi all, as some of the new GEF4 bundles we want to include with Mars specify javafx package imports (so far without version constraints), I was wondering what general policy we want to follow to ensure such kind of bundles can be properly resolved. Should we rely on the e(fx)clipse runtime bundles/fragments (org.eclipse.javafx and org.eclipse.fx.osgi), i.e. re-bundle them in our features or specify feature-dependencies to the enclosing e(fx)clipse runtime feature, or is there another intended way (it seems, e(fx)clipse has not announced its participation)? Cheers Alexander -- Dr. Alexander Nyßen Dipl.-Inform. Software-Engineer Telefon: +49 (0) 231 / 98 60-210 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0) 151 / 17396743 _ __http://www.itemis.de_ http://www.itemis.de/_ __alexander.nyssen@itemis.de_ mailto:alexander.nys...@itemis.de itemis AG Am Brambusch 15-24 44536 Lünen Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus [attachment signature.asc deleted by David M Williams/Raleigh/IBM] ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Dr. Alexander Nyßen Dipl.-Inform. Software-Engineer Telefon: +49 (0) 231 / 98 60-210 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0)
[cross-project-issues-dev] ATL participating in Mars release
Hi, ATL will be participating in Mars. The offset will be +2. Release record: https://projects.eclipse.org/projects/modeling.mmt.atl/releases/3.6.0 William attachment: william_piers.vcf___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] e(fx)clipse participating in Mars release
While you're at it, maybe it would be interesting to integrate e(fx)clipse in a package? Maybe the Java package? A bug report at [1] could help starting a discussion about this ;-) [1] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EPPcomponent=java-package Thanks, Markus On Wed, Aug 20, 2014 at 10:46 AM, Tom Schindl tom.schi...@bestsolution.at wrote: Hi, e(fx)clipse would like to join the Mars release as a +3 component because we depend on Xtext who is +2. Our current plan is to contribute e(fx)clipse 2.0 because this is the first time we are joining (I need to make myself familiar with the process) I'm not sure we manage to contribute to M1 in time. Tom ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] e4 tools (Incubation) participation in Mars?
To move the code out of the project, you need to do a restructuring review. Restructuring reviews are relatively simple affairs that require you describe (as concisely as possible) what needs to to change and why. To restructure by moving, you need a project to move the code into. This could be an existing project (e.g. PDT), or one that we create. If a new project is required, then we need to do a proposal followed by a creation review. We can combine the creation review with the restructuring review. There's more here: https://wiki.eclipse.org/Development_Resources/HOWTO/Restructuring_Reviews HTH, Wayne On 20/08/14 04:02 AM, Lars Vogel wrote: Hi Wayne, Thanks for the answer. Their are several Git repositories within in the e4 project and I would like to have the e4 tools Git repository available in the Mars update site. Sounds like we would need to migrate e4 tools to a new project. Would it be possible to move the e4 tools (they have their own Git repository) into a separate project? If yes, can you point me to the required process? Best regards, Lars 2014-08-12 22:16 GMT+02:00 Wayne Beaton wa...@eclipse.org mailto:wa...@eclipse.org: Sorry for the delay. e4 is a permanent incubator (i.e. no prospect of ever graduating). The EDP has this to say about permanent incubators: Permanent incubator projects never have releases; they cannot participate in the annual simultaneous release. Permanent incubators may have builds, and downloads. They conform to the standard incubation branding requirements and are subject to the IP due diligence rules outlined for incubating projects. Permanent incubators do not graduate. I believe that this aligns with the intent of e4. As functionality matures in e4, it is moved out and into a more permanent/stable home. If there is desire to change the nature of e4, then this is something that you can discuss with the Eclipse PMC. HTH, Wayne [1] http://www.eclipse.org/projects/dev_process/#4_9_Incubators On 30/07/14 05:06 AM, Lars Vogel wrote: Hi, The e4 tools project is still in incubation and we currently have no one working on changing that. If I open the Luna update site I see lots of incubation projects included in this update site. What is requirement to be included in the Mars update site? Best regards, Lars ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton @waynebeaton The Eclipse Foundation EclipseCon Europe 2014 https://www.eclipsecon.org/europe2014 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton @waynebeaton The Eclipse Foundation EclipseCon Europe 2014 https://www.eclipsecon.org/europe2014 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] e(fx)clipse participating in Mars release
You need to create a release record in the PMI: https://projects.eclipse.org/projects/technology.efxclipse/create-release Wayne On 20/08/14 04:46 AM, Tom Schindl wrote: Hi, e(fx)clipse would like to join the Mars release as a +3 component because we depend on Xtext who is +2. Our current plan is to contribute e(fx)clipse 2.0 because this is the first time we are joining (I need to make myself familiar with the process) I'm not sure we manage to contribute to M1 in time. Tom ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton @waynebeaton The Eclipse Foundation EclipseCon Europe 2014 https://www.eclipsecon.org/europe2014 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Status and outlook for Mars M1 and Luna SR1 RC1
Been a busy few days! I think we are on the verge of getting some green builds again, but wanted to be sure to mention some hacks I had to make: For Luna I disabled mylyn-docs-intent.b3aggrcon (I also removed eclipselink which I hope doesn't surprise them, as they were not participants in the Sim. Release! ... definitely need to tighten up our process! ) For Mars, more changes. In addition to the above two changes, the following contain some repo or feature disabled. The first one in the list (and the last) are the only ones I made ... but thought it'd be good to call attention to the others in case anyone is surprised. I also had to adjust the feature ranges of emf.transaction and gmf.runtime. emf-transaction I'm pretty sure was a typo, but the latter I'm not so sure. I changed (increased) feature ranges so it would match what was in the repo it was pointing at, but as far as I know it might have been pointing at the wrong repo? soa-bpmn2-modeler.b3aggrcon emf-emf-rap.b3aggrcon gef.b3aggrcon mft.b3aggrcon scout-rap.b3aggrcon swtbot.b3aggrcon mylyn-docs-intent.b3aggrcon Still a few hours left, if anyone can safely make changes to fix up things to be included, or accurate. The good news is I think the warm up RC has been effective in getting Luna close to lined up ... the next RC's, in a few weeks, will have little time for major changes, so I hope this preliminary step avoids problems for those that should be real release candidates. Also, more good news, I think this is the most M1 participants we've ever had! ... I am glad everyone is getting a good early start on Mars, as it should be. Thanks! ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Mars M1 and Luna SR1 RC1
Hi Dave, the emf.transaction was a indeed a typo and you are correct with your change. The gmf.runtime M1 build was pushed at right around the same time you were updating the b3aggrcon. I have just fixed with the correct b3aggrcon file. Cheers... Anthony From: David M Williams david_willi...@us.ibm.com To: cross-project-issues-dev@eclipse.org Date: 2014/08/20 03:09 PM Subject:[cross-project-issues-dev] Status and outlook for Mars M1 and LunaSR1 RC1 Sent by:cross-project-issues-dev-boun...@eclipse.org Been a busy few days! I think we are on the verge of getting some green builds again, but wanted to be sure to mention some hacks I had to make: For Luna I disabled mylyn-docs-intent.b3aggrcon (I also removed eclipselink which I hope doesn't surprise them, as they were not participants in the Sim. Release! ... definitely need to tighten up our process! ) For Mars, more changes. In addition to the above two changes, the following contain some repo or feature disabled. The first one in the list (and the last) are the only ones I made ... but thought it'd be good to call attention to the others in case anyone is surprised. I also had to adjust the feature ranges of emf.transaction and gmf.runtime. emf-transaction I'm pretty sure was a typo, but the latter I'm not so sure. I changed (increased) feature ranges so it would match what was in the repo it was pointing at, but as far as I know it might have been pointing at the wrong repo? soa-bpmn2-modeler.b3aggrcon emf-emf-rap.b3aggrcon gef.b3aggrcon mft.b3aggrcon scout-rap.b3aggrcon swtbot.b3aggrcon mylyn-docs-intent.b3aggrcon Still a few hours left, if anyone can safely make changes to fix up things to be included, or accurate. The good news is I think the warm up RC has been effective in getting Luna close to lined up ... the next RC's, in a few weeks, will have little time for major changes, so I hope this preliminary step avoids problems for those that should be real release candidates. Also, more good news, I think this is the most M1 participants we've ever had! ... I am glad everyone is getting a good early start on Mars, as it should be. Thanks! ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Mars M1 and Luna SR1 RC1
I just re-enabled those GEF4 features that only depend on EMF/Xtext but not on JavaFX. In case the e(fx)clipse contribution is yet added to the aggregation, I assume you might safely re-enable the remaining 6 GEF4 features as well. Cheers Alexander Am 20.08.2014 um 21:08 schrieb David M Williams david_willi...@us.ibm.com: Been a busy few days! I think we are on the verge of getting some green builds again, but wanted to be sure to mention some hacks I had to make: For Luna I disabled mylyn-docs-intent.b3aggrcon (I also removed eclipselink which I hope doesn't surprise them, as they were not participants in the Sim. Release! ... definitely need to tighten up our process! ) For Mars, more changes. In addition to the above two changes, the following contain some repo or feature disabled. The first one in the list (and the last) are the only ones I made ... but thought it'd be good to call attention to the others in case anyone is surprised. I also had to adjust the feature ranges of emf.transaction and gmf.runtime. emf-transaction I'm pretty sure was a typo, but the latter I'm not so sure. I changed (increased) feature ranges so it would match what was in the repo it was pointing at, but as far as I know it might have been pointing at the wrong repo? soa-bpmn2-modeler.b3aggrcon emf-emf-rap.b3aggrcon gef.b3aggrcon mft.b3aggrcon scout-rap.b3aggrcon swtbot.b3aggrcon mylyn-docs-intent.b3aggrcon Still a few hours left, if anyone can safely make changes to fix up things to be included, or accurate. The good news is I think the warm up RC has been effective in getting Luna close to lined up ... the next RC's, in a few weeks, will have little time for major changes, so I hope this preliminary step avoids problems for those that should be real release candidates. Also, more good news, I think this is the most M1 participants we've ever had! ... I am glad everyone is getting a good early start on Mars, as it should be. Thanks! ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Dr. Alexander Nyßen Dipl.-Inform. Software-Engineer Telefon: +49 (0) 231 / 98 60-210 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0) 151 / 17396743 http://www.itemis.de alexander.nys...@itemis.de itemis AG Am Brambusch 15-24 44536 Lünen Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus signature.asc Description: Message signed with OpenPGP using GPGMail ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Mars M1 and Luna SR1 RC1
Folks, And we backed stuff out. The other issue is fixed, but another issue came up! We'll try to get our CBI build working properly for RC2. FWIW, - Carl Anderson WTP Build guy | | From: | | --| |Carl Anderson/Raleigh/IBM@IBMUS | --| | | To:| | --| |Cross project issues cross-project-issues-dev@eclipse.org, | --| | | Cc:| | --| |Cross project issues cross-project-issues-dev@eclipse.org, cross-project-issues-dev-boun...@eclipse.org | --| | | Date: | | --| |08/20/2014 04:55 PM | --| | | Subject: | | --| |Re: [cross-project-issues-dev] Status and outlook for Mars M1 andLuna SR1 RC1| --| | | Sent by: | | --| |cross-project-issues-dev-boun...@eclipse.org | --| Folks, We just updated the WTP contribution. Our initial attempt failed due to bug 442169, but after a respin that issue appears to be fixed. FWIW, - Carl Anderson WTP Build guy Inactive hide details for Alexander Nyßen ---08/20/2014 04:50:02 PM---I just re-enabled those GEF4 features that only depend onAlexander Nyßen ---08/20/2014 04:50:02 PM---I just re-enabled those GEF4 features that only depend on EMF/Xtext but not on JavaFX. In case the e From:Alexander Nyßen alexander.nys...@itemis.de To: Cross project issues cross-project-issues-dev@eclipse.org, Date:08/20/2014 04:50 PM Subject: Re: [cross-project-issues-dev] Status and outlook for Mars M1 and Luna SR1 RC1 Sent by: cross-project-issues-dev-boun...@eclipse.org I just re-enabled those GEF4 features that only depend on
[cross-project-issues-dev] Staging and maintenance (staging) repos are complete
I believe we are as complete as we are going to be, for Luna SR1 RC1, and Mars M1. I've disabled the aggregation jobs, until Friday, to avoid confusion while EPP finishes up. Remember that Mars M1 (.../releases/staging) will be promoted to .../releases/mars, on Friday, approximately 9 or 10 AM, But, Luna SR1 RC1 (.../releases/maintenance) is not promoted anywhere. I typically do not promote anything new there, until closer to SR1 RC2 (but, will upon request). As always, just because the build succeeded, does not mean the build is correct, so test early and often ... and check the repo reports: Mars: http://build.eclipse.org/simrel/mars/reporeports/ Luna: http://build.eclipse.org/simrel/luna/reporeports/ Thanks everyone for your hard work this week (and leading up to this week, which I'm sure is just not as visible to me) but am confident it will pay off in a better quality Eclipse for the community, and adopters. Good job! ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
